[
https://issues.apache.org/jira/browse/CLOUDSTACK-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621540#comment-13621540
]
Sangeetha Hariharan commented on CLOUDSTACK-1837:
-------------------------------------------------
After upgrading the the binaries and before starting the management servers ,
following additional steps needs to be done:
1. If someone has made changes to your existing copy of the file
components.xml in your previous-version CloudStack installation , after upgrade
they will have to translate these changes into the current componentContext.xml
file which is located in
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/componentContext.xml.
2. If you have made changes to your existing copy of the
/etc/cloud/management/db.properties file in your previous-version CloudStack
installation, the changes will be preserved in the upgrade. However, you need
to do keep your db.properties file compatible 4.1 version of db.properties.
Following awsapi missing in db.properties when upgrading from 4.0 -> 4.1:
db.awsapi.username=
db.awsapi.password=
db.awsapi.host=
db.awsapi.port=
You have to add these entries to db.properties , if you want AWS query APIs to
work.
> Document additonal Steps to be included in the upgrade procedure from 4.0 ->
> 4.1
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1837
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1837
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.1.0
> Environment: Upgrade from 4.0 -> 4.1
> Reporter: Sangeetha Hariharan
> Assignee: Joe Brockmeier
> Priority: Critical
> Fix For: 4.1.0
>
>
> Additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included
> in the upgrade procedure from 4.0 -> 4.1
> Include the following steps as part of upgrade from 4.0 -> 4.1
>
> Step to restart all system Vms (SSVM,CPVM and Routers):
> 1. Run the following script to stop, then start, all Secondary Storage VMs,
> Console Proxy VMs, and virtual routers.Make sure port 8096 is open.
> Run the command once on one management server. Substitute your own IP
> address of the MySQL instance, the MySQL user to connect as, and the password
> to use for that user. In addition to those parameters, provide the "-a"
> arguments. For example:
> # nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -a >
> sysvm.log 2>&1 &
> # tail -f sysvm.log
> This might take up to an hour or more to run, depending on the number of
> accounts in the system.
> After the script terminates, check the log to verify correct execution:
> # tail -f sysvm.log
> The content should be like the following:
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> Done stopping and starting console proxy vm(s).
> Stopping and starting 4 running routing vm(s)...
> Done restarting router(s).
> Step 2:
> copy vhd-utils to /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver
--
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
