incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Nalley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-263) Document upgrade steps from 3.0.2 to 4.0
Date Sat, 06 Oct 2012 15:23:02 GMT

    [ 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

Mime
View raw message