You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2012/10/05 07:52:48 UTC
[jira] [Created] (CLOUDSTACK-263) Document upgrade steps from 3.0.2
to 4.0
Rohit Yadav created CLOUDSTACK-263:
--------------------------------------
Summary: Document upgrade steps from 3.0.2 to 4.0
Key: CLOUDSTACK-263
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
Project: CloudStack
Issue Type: Bug
Reporter: Rohit Yadav
Assignee: Jessica Tomechak
Fix For: 4.0.0
Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
1. Re-install cloud-scripts;
rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-263) Document upgrade steps from
3.0.2 to 4.0
Posted by "Rohit Yadav (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471066#comment-13471066 ]
Rohit Yadav commented on CLOUDSTACK-263:
----------------------------------------
Sorry I did not see the symlinking had no effect as we'd changed the paths in environment conf, that patch was in anticipation.
Alright, let's do it then and backing up is good. And, if we put the sed command in %post we can check $1 and do that only for upgrades; so something like:
%post
if [ '$1' == 2 ] ; then
cp -a /etc/cloud/agent.properties /etc/cloud/agent.properties.old
sed -i 's/com.cloud.agent.resource.computing.LibvirtComputingResource/com.cloud.hypervisor.kvm.resource.LibvirtComputingResource/g' /etc/cloud/agent/agent.properties
fi
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-263) Document upgrade steps from 3.0.2
to 4.0
Posted by "Chip Childers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chip Childers updated CLOUDSTACK-263:
-------------------------------------
Affects Version/s: pre-4.0.0
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-263) Document upgrade steps from
3.0.2 to 4.0
Posted by "Radhika Nair (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radhika Nair reassigned CLOUDSTACK-263:
---------------------------------------
Assignee: Radhika Nair (was: Jessica Tomechak)
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CLOUDSTACK-263) Document upgrade steps
from 3.0.2 to 4.0
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471042#comment-13471042 ]
David Nalley edited comment on CLOUDSTACK-263 at 10/6/12 3:21 PM:
------------------------------------------------------------------
IF we do that - lets first cp -a /etc/cloud/agent.properties /etc/cloud/agent.properties.old
I am generally against using %post, but don't think there is a really good alternative in this case. We should document that this happens just as a heads up for folks.
--David
was (Author: ke4qqq):
IF we do that - lets first cp -a /etc/cloud/agent.properties /etc/cloud/agent.properties.old
I am generally against using %post, but don't think there is a really good alternative in this case.
--David
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-263) Document upgrade steps from 3.0.2
to 4.0
Posted by "Alex Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Huang closed CLOUDSTACK-263.
---------------------------------
Resolution: Invalid
We don't need this if we fix 248 and 209 properly.
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-263) Document upgrade steps from
3.0.2 to 4.0
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470235#comment-13470235 ]
David Nalley commented on CLOUDSTACK-263:
-----------------------------------------
Why is there not a blocker bug for --force needing to be used?
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-263) Document upgrade steps from
3.0.2 to 4.0
Posted by "Rohit Yadav (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470950#comment-13470950 ]
Rohit Yadav commented on CLOUDSTACK-263:
----------------------------------------
In that case Edison, putting this command in %post scripts will do the trick, no need to even document it then;
%post scripts
sed -i 's/com.cloud.agent.resource.computing.LibvirtComputingResource/com.cloud.hypervisor.kvm.resource.LibvirtComputingResource/g' /etc/cloud/agent/agent.properties
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-263) Document upgrade steps from
3.0.2 to 4.0
Posted by "edison su (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470836#comment-13470836 ]
edison su commented on CLOUDSTACK-263:
--------------------------------------
Regarding to agent.properties upgrade issue:
The root cause is kvm resource file is moved from com.cloud.agent.resource.computing.LibvirtComputingResource to com.cloud.hypervisor.kvm.resource.LibvirtComputingResource during 3.0.x to 4.0.
What we really need do is to modify /etc/cloud/agent/agent.properties after upgrade:
sed -i 's/com.cloud.agent.resource.computing.LibvirtComputingResource/com.cloud.hypervisor.kvm.resource.LibvirtComputingResource/g' /etc/cloud/agent/agent.properties
Please document this step in the upgrade guide for kvm agent.
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-263) Document upgrade steps from 3.0.2
to 4.0
Posted by "Abhinav Roy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinav Roy updated CLOUDSTACK-263:
-----------------------------------
Priority: Blocker (was: Major)
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-263) Document upgrade steps from 3.0.2
to 4.0
Posted by "Abhinav Roy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinav Roy updated CLOUDSTACK-263:
-----------------------------------
Description:
Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
On both management server and KVM host
===================================
1. Re-install cloud-scripts;
rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
Only on KVM host
===================================
2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
(this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
was:
Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
1. Re-install cloud-scripts;
rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Reporter: Rohit Yadav
> Assignee: Jessica Tomechak
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-263) Document upgrade steps from
3.0.2 to 4.0
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471042#comment-13471042 ]
David Nalley commented on CLOUDSTACK-263:
-----------------------------------------
IF we do that - lets first cp -a /etc/cloud/agent.properties /etc/cloud/agent.properties.old
I am generally against using %post, but don't think there is a really good alternative in this case.
--David
> Document upgrade steps from 3.0.2 to 4.0
> ----------------------------------------
>
> Key: CLOUDSTACK-263
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-263
> Project: CloudStack
> Issue Type: Bug
> Affects Versions: pre-4.0.0
> Reporter: Rohit Yadav
> Assignee: Radhika Nair
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Refer: https://issues.apache.org/jira/browse/CLOUDSTACK-248
> Upgrade steps verified by Abhinav; applies for both upgrading of management server and agent;
> On both management server and KVM host
> ===================================
> 1. Re-install cloud-scripts;
> rpm -Uvh --force cloud-scripts-4.0.0-<build-id>.x86_64.rpm
> Only on KVM host
> ===================================
> 2. Move conf. parameters such as guid, host, workers, zone, pod etc. from /etc/cloud/agent/agent.properties to /etc/cloud/agent/agent.properties.rpmnew except for resource ( resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource ) and remove old file, rename /etc/cloud/agent/agent.properties.rpmnew to /etc/cloud/agent/agent.properties
> 3. Restart the cloud-agent services on host and cloud-management services on the management server after following steps 1 and 2.
> 4. Once the management server is up and running then we need to restart the virtual router for all the services to work properly.
> (this comment is from the bug https://issues.apache.org/jira/browse/CLOUDSTACK-126)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira