Citrix Systems 4.5 Printer User Manual


 
Chapter 9. Upgrading CloudPlatform to the Latest Version
48
Cloudstack Release 4.5.0 Thu Dec 18 18:51:22 UTC 2014
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.5.0 Thu Dec 18 18:51:22 UTC 2014
8. 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 “Setting Configuration Parameters” in the
Citrix CloudPlatform Administration Guide.
9. (XenServer only) Upgrade all existing XenServer clusters to XenServer 6.2 SP1 Hotfix
XS62ESP1005.
For more information, see Section 9.16.4, “Upgrading to XenServer 6.2 SP1 Hotfix
XS62ESP1005”.
For instructions for upgrading XenServer software and applying hotfixes, see Section 9.16.2,
“Applying Hotfixes to a XenServer Cluster ”.
10. (VMware only) After upgrade, you can change a Standard vSwitch zone to a VMware dvSwitch
zone, if required.
For more information, see Section 9.13, “Changing a Standard vSwitch Zone to a VMware
dvSwitch Zone (VMWare Only) ”
Post-Upgrade Considerations
Troubleshooting tip: If passwords which you know to be valid appear not to work after upgrade, or
other UI issues are seen, try clearing your browser cache and reloading the UI page.
(VMware only) After upgrade, whenever you add a new VMware cluster to a zone that was created
with a previous version of CloudPlatform, the fields vCenter host, vCenter Username, vCenter
Password, and vCenter Datacenter are required. The Add Cluster dialog in the CloudPlatform user
interface incorrectly shows them as optional, and will allow you to proceed with adding the cluster
even though these important fields are blank. If you do not provide the values, you will see an error
message like "Your host and/or path is wrong. Make sure it's of the format http://hostname/path".
We recommend you to use the following global configuration settings:
Global Parameter Value
deployment.planners.exclude SkipHeuresticsPlanner