From 139c622e255121acf3d2db73c16f5a892715b618 Mon Sep 17 00:00:00 2001 From: animesh Date: Sun, 22 Sep 2013 21:26:02 -0700 Subject: [PATCH] CLOUDSTACK-4245: Fixing the upgrade section to remove remnants from 4.1 upgrade steps which are not relevant any more --- docs/en-US/Release_Notes.xml | 42 ++---------------------------------- 1 file changed, 2 insertions(+), 40 deletions(-) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index a0b17c41a88..36dd9a55be7 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -1044,18 +1044,9 @@ under the License. If you run into any issues during upgrades, please feel free to ask questions on users@cloudstack.apache.org or dev@cloudstack.apache.org.
- Upgrade from 4.x.x to 4.2.0 - This section will guide you from &PRODUCT; 4.0.x versions to &PRODUCT; 4.2.0. + Upgrade from 4.1.x to 4.2.0 + This section will guide you from &PRODUCT; 4.1.x versions to &PRODUCT; 4.2.0. Any steps that are hypervisor-specific will be called out with a note. - - Package Structure Changes - The package structure for &PRODUCT; has changed significantly since the 4.0.x - releases. If you've compiled your own packages, you'll notice that the package names and - the number of packages has changed. This is not a bug. - However, this does mean that the procedure is not as simple as an apt-get - upgrade or yum update, so please follow this section - carefully. - 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. @@ -1092,35 +1083,6 @@ under the License. You'll be prompted for your password. # mysqldump -u root -p cloud > cloudstack-backup.sql - - If you have made changes to - /etc/cloud/management/components.xml, you'll need to carry these - over manually to the new file, - /etc/cloudstack/management/componentContext.xml. This is not done - automatically. (If you're unsure, we recommend making a backup of the original - components.xml to be on the safe side. - - - After upgrading to 4.2, API clients are expected to send plain text passwords for - 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) - -<!-- Security adapters --> -<bean id="userAuthenticators" class="com.cloud.utils.component.AdapterList"> - <property name="Adapters"> - <list> - <ref bean="PlainTextUserAuthenticator"/> - <ref bean="MD5UserAuthenticator"/> - <ref bean="LDAPUserAuthenticator"/> - </list> - </property> -</bean> - - PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to - 4.2. - If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step .