Upgrade from 4.2.0 to 4.2.1

Upgrade from 4.2.0 to 4.2.1 - This section will guide you to upgrade from &PRODUCT; 4.2 to &PRODUCT; 4.2.1. Any steps - that are hypervisor-specific will be called out with a note. We recommend reading through - this section once or twice before beginning your upgrade procedure, and working through it - on a test system before working on a production system. - Most users of &PRODUCT; manage the installation and upgrades of &PRODUCT; with one of - Linux's predominant package systems, RPM or APT. This guide assumes you are using RPM and - Yum for Red Hat Enterprise Linux or CentOS, or APT and Debian packages for Ubuntu. - - The following upgrade instructions should be performed regardless of hypervisor - type. - + This section will guide you from &PRODUCT; 4.2 to &PRODUCT; 4.2.1. + Any steps that are hypervisor-specific will be called out with a note. + We recommend reading through this section once or twice before beginning your upgrade + procedure, and working through it on a test system before working on a production + system. + + The following upgrade instructions should be performed regardless of hypervisor + type. + @@ -2002,20 +2000,26 @@ under the License. - Create RPM or Debian packages as appropriate and a repository from the 4.2.1 source, - or check the Apache CloudStack downloads page at Most users of &PRODUCT; manage the installation and upgrades of &PRODUCT; with one + of Linux's predominant package systems, RPM or APT. This guide assumes you'll be using + RPM and Yum (for Red Hat Enterprise Linux or CentOS), or APT and Debian packages (for + Ubuntu). + + + Create RPM or Debian packages (as appropriate) and a repository from the 4.2.1 + source, or check the Apache CloudStack downloads page at http://cloudstack.apache.org/downloads.html for package repositories supplied - by community members. - You will need them for step or step - . Instructions for creating packages from - the &PRODUCT; source are in the or step . + Instructions for creating packages from the &PRODUCT; source are in the Installation Guide. - Stop your management server or servers. - Run the following on all the Management Server hosts: + Stop your management server or servers. Run this on all management server + hosts: # service cloudstack-management stop @@ -2045,9 +2049,9 @@ under the License. Verify signatures and hash files: - gpg --verify apache-cloudstack-4.2.0-src.tar.bz2.asc - gpg --print-md MD5 apache-cloudstack-4.2.0-src.tar.bz2 | diff - apache-cloudstack-4.2.0-src.tar.bz2.md5 -gpg --print-md SHA512 apache-cloudstack-4.2.0-src.tar.bz2 | diff - apache-cloudstack-4.2.0-src.tar.bz2.sha + #gpg --verify apache-cloudstack-4.2.1-src.tar.bz2.asc +#gpg --print-md MD5 apache-cloudstack-4.2.1-src.tar.bz2 | diff - apache-cloudstack-4.2.1-src.tar.bz2.md5 +#gpg --print-md SHA512 apache-cloudstack-4.2.1-src.tar.bz2 | diff - apache-cloudstack-4.2.1-src.tar.bz2.sha Each of these commands should return no output. Any output from them implies that there is a difference between the hash you generated locally and the hash that has been pulled from the server. @@ -2095,8 +2099,9 @@ gpg --print-md SHA512 apache-cloudstack-4.2.0-src.tar.bz2 | diff - apache-clouds storage needs to be verified to ensure it passes new validation. Check local storage by querying the cloud.storage_pool table: #mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" - If local storage paths are found to have a trailing forward slash, remove it: - #mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + If local storage paths are found to have a trailing forward slash, remove it: + #mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + If you are using Ubuntu, follow this procedure to upgrade your packages. If not, @@ -2109,39 +2114,38 @@ gpg --print-md SHA512 apache-cloudstack-4.2.0-src.tar.bz2 | diff - apache-clouds - Change the sources list for each system with &PRODUCT; packages. - This means all management servers, and any hosts that have the KVM agent. No - changes should be necessary for hosts that are running VMware or XenServer - - - Open /etc/apt/sources.list.d/cloudstack.list on any systems - that have &PRODUCT; packages installed. + The first order of business will be to change the sources list for each system + with &PRODUCT; packages. This means all management servers, and any hosts that have + the KVM agent. (No changes should be necessary for hosts that are running VMware or + Xen.) + Start by opening /etc/apt/sources.list.d/cloudstack.list on + any systems that have &PRODUCT; packages installed. This file should have one line, which contains: + deb http://cloudstack.apt-get.eu/ubuntu precise 4.0 + We'll change it to point to the new package repository: deb http://cloudstack.apt-get.eu/ubuntu precise 4.2 + If you're using your own package repository, change this line to read as + appropriate for your 4.2.1 repository. - Change it to point to the new package - repository:deb http://cloudstack.apt-get.eu/ubuntu precise 4.2.1If - you're using your own package repository, change this line to read as appropriate for - your 4.2.1 repository. - Update your APT package list: + Now update your apt package list: $ sudo apt-get update - Install the cloudstack-management package. - This fetches in any other dependencies you need. + Now that you have the repository configured, it's time to install the + cloudstack-management package. This will pull in any other + dependencies you need. $ sudo apt-get install cloudstack-management - Manually install the cloudstack-agent package: + You will need to manually install the cloudstack-agent + package: $ sudo apt-get install cloudstack-agent During the installation of cloudstack-agent, APT will copy your agent.properties, log4j-cloud.xml, and environment.properties from /etc/cloud/agent to /etc/cloudstack/agent. - - When prompted whether you wish to keep your configuration, say Yes. @@ -2153,9 +2157,11 @@ gpg --print-md SHA512 apache-cloudstack-4.2.0-src.tar.bz2 | diff - apache-clouds Restart the agent: - service cloudstack-agent stop + +service cloudstack-agent stop killall jsvc -service cloudstack-agent start +service cloudstack-agent start + @@ -2170,7 +2176,7 @@ service cloudstack-agent start Generate the encrypted equivalent of your vCenter password: - java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false + java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false Store the output from this step, we need to add this in cluster_details table and vmware_data_center tables in place of the plain text password @@ -2181,7 +2187,7 @@ service cloudstack-agent start Update the plain text password with the encrypted one - update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_; + update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_; Confirm that the table is updated: @@ -2462,8 +2468,9 @@ Done restarting router(s). storage needs to be verified to ensure it passes new validation. Check local storage by querying the cloud.storage_pool table: #mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'" - If local storage paths are found to have a trailing forward slash, remove it: - #mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + If local storage paths are found to have a trailing forward slash, remove it: + #mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"'; + If you are using Ubuntu, follow this procedure to upgrade your packages. If not, @@ -2538,7 +2545,7 @@ service cloudstack-agent start Generate the encrypted equivalent of your vCenter password: - java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false + java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false Store the output from this step, we need to add this in cluster_details table and vmware_data_center tables in place of the plain text password @@ -2549,7 +2556,7 @@ service cloudstack-agent start Update the plain text password with the encrypted one - update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_; + update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_; Confirm that the table is updated: @@ -2830,7 +2837,7 @@ Done restarting router(s). Make a backup of your MySQL database. If you run into any issues or need to roll back the upgrade, this will assist in debugging or restoring your existing environment. You'll be prompted for your password. - # mysqldump -u root -p cloud > cloudstack-backup.sql + # mysqldump -u root -p cloud > cloudstack-backup.sql Whether you're upgrading a Red Hat/CentOS based system or Ubuntu based system, @@ -3194,8 +3201,8 @@ Done restarting router(s). In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password. - # mysqldump -u root -pmysql_password cloud > cloud-backup.dmp - # mysqldump -u root -pmysql_password cloud_usage > cloud-usage-backup.dmp + # mysqldump -u root -pmysql_password cloud > cloud-backup.dmp + # mysqldump -u root -pmysql_password cloud_usage > cloud-usage-backup.dmp Either build RPM/DEB packages as detailed in the Installation Guide, or use one of @@ -3840,8 +3847,8 @@ service cloudstack-agent start In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password. - # mysqldump -u root -pmysql_password cloud > cloud-backup.dmp - # mysqldump -u root -pmysql_password cloud_usage > cloud-usage-backup.dmp + # mysqldump -u root -pmysql_password cloud > cloud-backup.dmp + # mysqldump -u root -pmysql_password cloud_usage > cloud-usage-backup.dmp @@ -4212,7 +4219,7 @@ service cloudstack-agent start # ssh -i private-key-path link-local-ip -p 3922 # cat /etc/cloudstack-release The output should be like the following: - Cloudstack Release 4.2.1 Mon Dec 9 15:10:04 PST 2013 + Cloudstack Release 4.0.0-incubating Mon Oct 9 15:10:04 PST 2012 ESXi SSH in using the private IP address of the system VM. For example, in the command