cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject git commit: updated refs/heads/master to 57fea8f
Date Tue, 09 Apr 2013 17:39:24 GMT
Updated Branches:
  refs/heads/master 6c9fcb8c8 -> 57fea8f90

CLOUDSTACK-1837: Documenting steps from this bug for upgrade procedure from 4.0 to 4.1. Unsure
how these translate for earlier CloudStack versions.


Branch: refs/heads/master
Commit: 57fea8f90cda8aa39363d519e5d35d87ab82072e
Parents: 6c9fcb8
Author: Joe Brockmeier <>
Authored: Tue Apr 9 12:38:29 2013 -0500
Committer: Joe Brockmeier <>
Committed: Tue Apr 9 12:39:12 2013 -0500

 docs/en-US/Release_Notes.xml |   23 ++++++++++++++++++++++-
 1 files changed, 22 insertions(+), 1 deletions(-)
diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml
index b8465ed..00cbc49 100644
--- a/docs/en-US/Release_Notes.xml
+++ b/docs/en-US/Release_Notes.xml
@@ -54,6 +54,26 @@ under the License.
                     <para>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.</para>
                     <programlisting># mysqldump -u root -p cloud &gt; cloudstack-backup.sql</programlisting>
+                <listitem>
+                    <para>Whether you're upgrading a Red Hat/CentOS based system or
Ubuntu based system, you're going to need to stop the CloudStack management server before
+                    <programlisting language="Bash"># service cloud-management stop</programlisting>
+                </listitem>
+                <listitem>
+                    <para>If you have made changes to <filename>/etc/cloud/management/components.xml</filename>,
you'll need to carry these over manually to the new file, <filename>/etc/cloudstack/management/componentContext.xml</filename>.
This is not done automatically. (If you're unsure, we recommend making a backup of the original
<filename>components.xml</filename> to be on the safe side.</para>
+                </listitem>
+                <listitem>
+                    <note><title>For AWS API Users Only</title>
+                        <para>This step is only necessary if you're using the AWS APIs
with &PRODUCT;. If not, you can skip this step.</para>
+                    </note>
+                    <para>The file <filename>/etc/cloud/management/</filename>
will be carried over to <filename>etc/cloudstack/management/</filename>,
but the parameters for the AWS API are <emphasis>not</emphasis> carried over.
You'll need to add these parameters to the new file manually:</para>
+                    <programlisting language="Bash">
+                    </programlisting>
+                    <para>For the AWS API queries to work, you'll need to copy those
over to <filename>/etc/cloudstack/management/</filename> (with the
values you have currently).</para>
+                </listitem>
                 <listitem id="upgrade-deb-packages">
                     <para>If you are using Ubuntu, follow this procedure to upgrade
your packages. If not, skip to step <xref linkend="upgrade-rpm-packages" />.</para>

                     <note><title>Community Packages</title>
@@ -74,7 +94,8 @@ under the License.
                             <programlisting language="Bash">$ sudo apt-get update</programlisting>
                         <listitem id="deb-master">
-                            <para>### upgrade steps for Debian on master servers goes
+                            <para>Now that you have the repository configured, it's
time to install the <filename>cloudstack-management</filename> package. This will
pull in any other dependencies you need.</para>
+                            <programlisting language="Bash">$ sudo apt-get install
                         <listitem id="kvm-agent-deb">
                             <para>You will need to manually install the <filename>cloudstack-agent</filename>

View raw message