From 88a58cb157a22226e90b50db946e5be97aa03733 Mon Sep 17 00:00:00 2001 From: Radhika PC Date: Fri, 23 Aug 2013 12:11:23 +0530 Subject: [PATCH] CLOUDSTACK-4469 upgrade exception added to known issues --- docs/en-US/Release_Notes.xml | 6299 +++++++++++++++++++++++++++++++++- 1 file changed, 6206 insertions(+), 93 deletions(-) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index 338af85c391..ca1e19251e3 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -21,7 +21,7 @@ under the License. - + Welcome to &PRODUCT; 4.2 Welcome to the 4.2.0 release of &PRODUCT;, the second major release from the Apache CloudStack project since its graduation from the Apache Incubator. &PRODUCT; 4.2 includes more @@ -57,10 +57,23 @@ under the License. Version 4.2.0 -
+
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. +
+ Windows 8 and Windows Server as VM Guest OS + Supported on XenServer, VMware, and KVM. + Windows 8 and Windows Server 2012 can now be used as OS types on guest virtual + machines. The OS would be made available the same as any other, by uploading an ISO or a + template. The instructions for uploading ISOs and templates are given in the + Administrator's Guide. + + Limitation: When used with VMware hosts, this + feature works only for the following versions: vSphere ESXi 5.1 and ESXi 5.0 Patch + 4. + +
Portable IPs
-
- Resize Volumes Feature - ### -
-
- - <para>###</para> - </section> - <section id="api-throttling"> - <title>API Request Throttling - CLOUDSTACK-618: Limits the number of API requests per second that can be placed - against a management server to avoid DoS attacks via API requests. - The throttling is controlled by the api.throttling.enabled, - api.throttling.interval, and api.throttling.max - configuration settings. Note that api.throttling.enabled is set to - false by default. -
-
- Windows 8 and Windows Server as VM Guest OS - Supported on XenServer, VMware, and KVM. - Windows 8 and Windows Server 2012 can now be used as OS types on guest virtual - machines. The OS would be made available the same as any other, by uploading an ISO or a - template. The instructions for uploading ISOs and templates are given in the - Administrator's Guide. - - Limitation: When used with VMware hosts, this - feature works only for the following versions: vSphere ESXi 5.1 and ESXi 5.0 Patch - 4. - -
-
- S3 Backed Secondary Storage - CLOUDSTACK-509: This enhancement backs NFS secondary storage with an - S3-compatible object store. Periodically, a reaper thread synchronizes the templates, - ISOs, and snapshots stored on a NFS secondary storage mount with a configured S3 object - store. In addition to permitting the use of commodity or IaaS storage solutions for static - assets, it provides a means of automatically synchronizing template and ISO assets across - multiple zones. - See the &PRODUCT; - wiki for more information on this feature, currently the documentation is - incomplete. -
-
- User and Domain Admin Can Create API Key and Secret - CLOUDSTACK-437: This feature adds the ability for domain admins and users to - create their own API Key and Secret. Domain admins can create keys for themselves, - subdomain admins, and for regular users, but not for other domain admins. -
-
- Support Inline Mode for F5 and SRX - CLOUDSTACK-306: For &PRODUCT; deployments using the Juniper SRX (firewall) and - F5 Big IP (load balancer), &PRODUCT; 4.2.0 supports putting the firewall in front of the - load balancer, making the firewall device the gateway and putting the load balancer behind - the public network. -
-
- Egress Firewall Rules for Guest Networks - CLOUDSTACK-299: This feature allows users to create egress (exit) traffic rules - from private networks to public networks (e.g. from your internal - network to the public Internet). By default all traffic is blocked from internal networks - to the public networks, this allows you to open ports as necessary. - Egress traffic rules are suppored only on virtual routers at this time, physical - devices are not supported. -
-
- Reset SSH Key to Access VM - CLOUDSTACK-297: &PRODUCT; 4.2.0 introduces a new API - resetSSHKeyForVirtualMachine, that can allow them to set or reset the - SSH keypair assigned to a virtual machine. -
-
+
Issues Fixed in 4.2.0 Apache CloudStack uses Jira to track its issues. All new features and bugs for 4.2.0 have been tracked @@ -438,8 +373,8 @@ under the License. Known Issues in 4.2.0 - - + + @@ -451,6 +386,20 @@ under the License. + + CLOUDSTACK-4207 + + The following exception is observed when the Management Server is started + after upgrade from any older versions to &PRODUCT; 4.2. + jsonParseException: The JsonDeserializer + com.cloud.agent.transport.ArrayTypeAdaptor@2426e26f failed to deserialize json + object + Ignore this exception, this would stop after you upgrade the System VM. + However, if you want to prevent this, stop system VM from the hypervisor before + upgrade. + + CLOUDSTACK-2709 @@ -758,6 +707,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 . @@ -994,7 +1016,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 @@ -1064,6 +1086,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 . @@ -1196,11 +1244,9 @@ 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. - + 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 @@ -1756,8 +1802,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) @@ -1843,6 +1889,32 @@ 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 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) Perform the following additional steps on 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 your CloudStack package repositories as outlined in the Installation @@ -2102,7 +2174,6048 @@ service cloudstack-agent start
-