Filter
Top Products
Upgrade from 3.0.x to 4.2
27
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).
c. If you would like additional confirmation that the new system VM templates were correctly
applied when these system VMs were rebooted, SSH into the System VM and check the
version.
Use one of the following techniques, depending on the hypervisor.
XenServer or KVM:
SSH in by using the link local IP address of the system VM. For example, in the command
below, substitute your own path to the private key used to log in to the system VM and your
own link local IP.
Run the following commands on the XenServer or KVM host on which the system VM is
present:
# ssh -i /root/.ssh/id_rsa.cloud <link-local-ip> -p 3922
# cat /etc/cloudstack-release
The output should be like the following:
Cloudstack Release 4.2 Mon Aug 12 15:10:04 PST 2013
ESXi
SSH in using the private IP address of the system VM. For example, in the command below,
substitute your own path to the private key used to log in to the system VM and your own
private IP.
Run the following commands on the Management Server:
# ssh -i /var/cloudstack/management/.ssh/id_rsa <private-ip> -p 3922
# cat /etc/cloudstack-release
The output should be like the following:
Cloudstack Release 4.2 Mon Sep 24 15:10:04 PST 2012
21. If you want to close the admin port again (recommended in production systems), set
integration.api.port to null. Then restart the Management Server. For information about how to set
integration.api.port, see Section 5.5, “Setting Configuration Parameters”.
22. (XenServer only) If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to
a version supported by CloudPlatform 4.2 and apply any required hotfixes. Instructions for
upgrading XenServer software and applying hotfixes can be found in Section 4.4, “Upgrading and
Hotfixing XenServer Hypervisor Hosts”.