From 5980faf9a7f811bdc10732ae3f4cdbe21534e19b Mon Sep 17 00:00:00 2001 From: Radhika PC Date: Thu, 22 Aug 2013 16:46:23 +0530 Subject: [PATCH] CLOUDSTACK-4185 vmware steps for upgrade paths --- docs/en-US/Release_Notes.xml | 234 +++++++++++++++++++++++++++++++++-- 1 file changed, 225 insertions(+), 9 deletions(-) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index 8534b0815f3..d4550065c4e 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -60,7 +60,7 @@ under the License.
What’s New in 4.2 Apache CloudStack 4.2.0 includes many new features. This section covers the most - prominent new features and changes. + prominent new features and changes.
Windows 8 and Windows Server as VM Guest OS Supported on XenServer, VMware, and KVM. @@ -693,6 +693,79 @@ service cloudstack-agent restart + + (VMware only) Additional steps are required for each VMware cluster. These steps + will not affect running guests in the cloud. These steps are required only for clouds + using VMware clusters: + + + Stop the Management Server: + service cloudstack-management stop + + + 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 + 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 + + + Find the ID of the row of cluster_details table that you have to update: + mysql -u <username> -p<password> + select * from cloud.cluster_details; + + + 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_; + + + Confirm that the table is updated: + select * from cloud.cluster_details; + + + Find the ID of the correct row of vmware_data_center that you want to + update + select * from cloud.vmware_data_center; + + + update the plain text password with the encrypted one: + update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_; + + + Confirm that the table is updated: + select * from cloud.vmware_data_center; + + + Start the &PRODUCT; Management server + service cloudstack-management start + + + + + (KVM only) Additional steps are required for each KVM host. These steps will not + affect running guests in the cloud. These steps are required only for clouds using KVM + as hosts and only on the KVM hosts. + + + Copy the CloudPlatform 4.2 tar file to the host, untar it, and change directory + to the resulting directory. + + + Stop the running agent. + # service cloud-agent stop + + + Update the agent software. + # ./install.sh + + + Choose "U" to update the packages. + + + Start the agent. + # service cloudstack-agent start + + + If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step . @@ -929,7 +1002,7 @@ Done restarting router(s). If you've created your own packages and APT repository, substitute your own URL for the ones used in these examples. - + 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 @@ -999,6 +1072,32 @@ service cloudstack-agent restart + + (KVM only) Additional steps are required for each KVM host. These steps will not + affect running guests in the cloud. These steps are required only for clouds using KVM + as hosts and only on the KVM hosts. + + + Copy the CloudPlatform 4.2 tar file to the host, untar it, and change directory + to the resulting directory. + + + Stop the running agent. + # service cloud-agent stop + + + Update the agent software. + # ./install.sh + + + Choose "U" to update the packages. + + + Start the agent. + # service cloudstack-agent start + + + If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step . @@ -1131,11 +1230,55 @@ service cloudstack-agent start # service cloudstack-usage start - - Additional steps are required for each KVM host. These steps will not affect - running guests in the cloud. These steps are required only for clouds using KVM as - hosts and only on the KVM hosts. - + (VMware only) Additional steps are required for each VMware cluster. These steps will not affect running guests in + the cloud. These steps are required only for clouds using VMware clusters: + + + Stop the Management Server: + service cloudstack-management stop + + + 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 + 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 + + + Find the ID of the row of cluster_details table that you have to update: + mysql -u <username> -p<password> + select * from cloud.cluster_details; + + + 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_; + + + Confirm that the table is updated: + select * from cloud.cluster_details; + + + Find the ID of the correct row of vmware_data_center that you want to + update + select * from cloud.vmware_data_center; + + + update the plain text password with the encrypted one: + update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_; + + + Confirm that the table is updated: + select * from cloud.vmware_data_center; + + + Start the &PRODUCT; Management server + service cloudstack-management start + + + + + Additional steps are required for each KVM host. These steps will not affect running + guests in the cloud. These steps are required only for clouds using KVM as hosts and + only on the KVM hosts. Configure a yum or apt repository containing the &PRODUCT; packages as outlined @@ -1691,8 +1834,8 @@ service cloudstack-agent start After upgrading to 4.2, API clients are expected to send plain text passwords for - login and user creation, instead of MD5 hash. Incase, api client changes are not - acceptable, following changes are to be made for backward compatibility: + login and user creation, instead of MD5 hash. If API client changes are not acceptable, + following changes are to be made for backward compatibility: Modify componentsContext.xml, and make PlainTextUserAuthenticator as the default authenticator (1st entry in the userAuthenticators adapter list is default) @@ -1774,6 +1917,79 @@ service cloudstack-agent start this on each Usage Server host. # service cloudstack-usage start + + (VMware only) Additional steps are required for each VMware cluster, if you are + upgrading from version 3.0.4 or beyond. These steps will not affect running guests in + the cloud. These steps are required only for clouds using VMware clusters: + + + Stop the Management Server: + service cloudstack-management stop + + + 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 + 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 + + + Find the ID of the row of cluster_details table that you have to update: + mysql -u <username> -p<password> + select * from cloud.cluster_details; + + + 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_; + + + Confirm that the table is updated: + select * from cloud.cluster_details; + + + Find the ID of the correct row of vmware_data_center that you want to + update + select * from cloud.vmware_data_center; + + + update the plain text password with the encrypted one: + update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_; + + + Confirm that the table is updated: + select * from cloud.vmware_data_center; + + + Start the &PRODUCT; Management server + service cloudstack-management start + + + + + (KVM only) Additional steps are required for each KVM host. These steps will not + affect running guests in the cloud. These steps are required only for clouds using KVM + as hosts and only on the KVM hosts. + + + Copy the CloudPlatform 4.2 tar file to the host, untar it, and change directory + to the resulting directory. + + + Stop the running agent. + # service cloud-agent stop + + + Update the agent software. + # ./install.sh + + + Choose "U" to update the packages. + + + Start the agent. + # service cloudstack-agent start + + + (KVM only) Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM