You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by pd...@apache.org on 2014/11/29 17:01:20 UTC
[12/13] cloudstack-docs-rn git commit: updated for 4.4.2 release
updated for 4.4.2 release
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/commit/5ab48e4c
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/tree/5ab48e4c
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/diff/5ab48e4c
Branch: refs/heads/master
Commit: 5ab48e4cc0d23bcb34f23669b92582e68362b6d0
Parents: 4a05f53
Author: Pierre-Luc Dion <pd...@apache.org>
Authored: Sat Nov 29 10:54:31 2014 -0500
Committer: Pierre-Luc Dion <pd...@apache.org>
Committed: Sat Nov 29 10:54:31 2014 -0500
----------------------------------------------------------------------
source/about.rst | 2 +-
source/api-changes.rst | 4 +-
source/conf.py | 2 +-
source/fixed_issues.rst | 31 ++-
source/index.rst | 3 +-
source/known_issues.rst | 46 +++-
source/upgrade/upgrade-4.4.0.rst | 380 ++++++++++++++++++++++++++++++++++
source/upgrade/upgrade-4.4.1.rst | 358 ++++++++++++++++++++++++++++++++
source/upgrade/upgrade-4.4.rst | 380 ----------------------------------
9 files changed, 816 insertions(+), 390 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/about.rst
----------------------------------------------------------------------
diff --git a/source/about.rst b/source/about.rst
index 1eb40c1..d6e7b88 100644
--- a/source/about.rst
+++ b/source/about.rst
@@ -17,7 +17,7 @@
What's New in |version|
=======================
-CloudStack |release| is a bugfix release and does not add new features to |version|. Here is the list of new features and improvements introduce in |version|:
+Version |release| of Apache CloudStack is a bugfix release and does not add new features to |version|. Here is the list of new features and improvements introduce in |version|:
.. contents::
:local:
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/api-changes.rst
----------------------------------------------------------------------
diff --git a/source/api-changes.rst b/source/api-changes.rst
index ad003e5..221c713 100644
--- a/source/api-changes.rst
+++ b/source/api-changes.rst
@@ -17,8 +17,8 @@
API Changes Introduced in |version|
===================================
-API Changes Introduced in |release|
------------------------------------
+API Changes Introduced in 4.4.1
+-------------------------------
updateSnapshotPolicy (Updates the snapshot policy.)
+-----------------------------------+-------------------------------------------------------------------------------------------+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/conf.py
----------------------------------------------------------------------
diff --git a/source/conf.py b/source/conf.py
index 8f8bf42..7d1b504 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -75,7 +75,7 @@ copyright = u'2014, Apache CloudStack'
# The short X.Y version.
version = '4.4'
# The full version, including alpha/beta/rc tags.
-release = '4.4.1'
+release = '4.4.2'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/fixed_issues.rst
----------------------------------------------------------------------
diff --git a/source/fixed_issues.rst b/source/fixed_issues.rst
index 60865ff..4a82ce2 100644
--- a/source/fixed_issues.rst
+++ b/source/fixed_issues.rst
@@ -14,16 +14,41 @@
under the License.
-Issues Fixed in |release|
--------------------------
+Issues Fixed in |version|
+=========================
Apache CloudStack uses `Jira <https://issues.apache.org/jira/browse/CLOUDSTACK>`_
to track its issues. All new features and bugs for |release| have been tracked
in Jira, and have a standard naming convention of "CLOUDSTACK-NNNN" where
"NNNN" is the issue number.
+Issues Fixed in |release|
+-------------------------
+
+For the list of issues fixed, see `Issues Fixed in
+<https://issues.apache.org/jira/issues/?filter=12329678>`_ |release|.
+
+========================================================================== ===================================================================================
+Bug ID Description
+========================================================================== ===================================================================================
+`CLOUDSTACK-7952 <https://issues.apache.org/jira/browse/CLOUDSTACK-7952>`_ listSslCerts returns private key...
+`CLOUDSTACK-7906 <https://issues.apache.org/jira/browse/CLOUDSTACK-7906>`_ certificate tests fail in CertServiceTest.java...
+`CLOUDSTACK-7887 <https://issues.apache.org/jira/browse/CLOUDSTACK-7887>`_ fail to push snapshot to secondary storage if using multipart using swift...
+`CLOUDSTACK-7883 <https://issues.apache.org/jira/browse/CLOUDSTACK-7883>`_ Allow infrastructure to handle delete of volume from DB...
+`CLOUDSTACK-7871 <https://issues.apache.org/jira/browse/CLOUDSTACK-7871>`_ Fix update VirtualMachine/Template API to allow nic/disk controller details for ...
+`CLOUDSTACK-7855 <https://issues.apache.org/jira/browse/CLOUDSTACK-7855>`_ Sec storage/network MTU should be on nic3 and not nic1...
+`CLOUDSTACK-7826 <https://issues.apache.org/jira/browse/CLOUDSTACK-7826>`_ UI - dialog widget - dependent dropdown field (dependsOn property specified) - f...
+`CLOUDSTACK-7822 <https://issues.apache.org/jira/browse/CLOUDSTACK-7822>`_ test SSL cert expired...
+`CLOUDSTACK-7752 <https://issues.apache.org/jira/browse/CLOUDSTACK-7752>`_ Management Server goes in infinite loop while creating a vm with tagged local da...
+`CLOUDSTACK-7722 <https://issues.apache.org/jira/browse/CLOUDSTACK-7722>`_ add.label: Add button for tags show the label not "Add" text...
+`CLOUDSTACK-7246 <https://issues.apache.org/jira/browse/CLOUDSTACK-7246>`_ VM deployment failed due to wrong in script name createipalias.sh...
+========================================================================== ===================================================================================
+
+Issues Fixed in 4.4.1
+---------------------
+
For the list of issues fixed, see `Issues Fixed in
-<https://issues.apache.org/jira/issues/?filter=12329271>`_ |release|.
+<https://issues.apache.org/jira/issues/?filter=12329271>`_ 4.4.1.
========================================================================== ===================================================================================
Bug ID Description
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/index.rst
----------------------------------------------------------------------
diff --git a/source/index.rst b/source/index.rst
index a16c358..ebabfe8 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -67,7 +67,8 @@ Contents:
.. toctree::
:maxdepth: 1
- upgrade/upgrade-4.4
+ upgrade/upgrade-4.4.1
+ upgrade/upgrade-4.4.0
upgrade/upgrade-4.3
upgrade/upgrade-4.2
upgrade/upgrade-4.1
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/known_issues.rst
----------------------------------------------------------------------
diff --git a/source/known_issues.rst b/source/known_issues.rst
index 15b11f9..e2d711a 100644
--- a/source/known_issues.rst
+++ b/source/known_issues.rst
@@ -13,7 +13,6 @@
specific language governing permissions and limitations
under the License.
-
Known Issues in |release|
=========================
@@ -23,8 +22,51 @@ new features and bugs for |release| have been tracked in Jira, and have a
standard naming convention of "CLOUDSTACK-NNNN" where "NNNN" is the issue
number.
+
+Discovered in |version|
+-----------------------
+
+========================================================================== ===================================================================================
+Bug ID Description
+========================================================================== ===================================================================================
+`CLOUDSTACK-7988 <https://issues.apache.org/jira/browse/CLOUDSTACK-7988>`_ Template status is empty while the template is creating....
+`CLOUDSTACK-7936 <https://issues.apache.org/jira/browse/CLOUDSTACK-7936>`_ System VM's are getting stuck in starting mode after Hypervisor reboot...
+`CLOUDSTACK-7926 <https://issues.apache.org/jira/browse/CLOUDSTACK-7926>`_ Don't immediately delete volumes - have the pruge thread do it...
+`CLOUDSTACK-7907 <https://issues.apache.org/jira/browse/CLOUDSTACK-7907>`_ UI heavily broken...
+`CLOUDSTACK-7903 <https://issues.apache.org/jira/browse/CLOUDSTACK-7903>`_ Decrease minimal usage aggregation range value...
+`CLOUDSTACK-7888 <https://issues.apache.org/jira/browse/CLOUDSTACK-7888>`_ unable to create remote vpn because of special character in password...
+`CLOUDSTACK-7874 <https://issues.apache.org/jira/browse/CLOUDSTACK-7874>`_ "CPU (in MHz)" does not make sense...
+`CLOUDSTACK-7858 <https://issues.apache.org/jira/browse/CLOUDSTACK-7858>`_ Implement separate network throttling rate on VR's Public NIC...
+`CLOUDSTACK-7857 <https://issues.apache.org/jira/browse/CLOUDSTACK-7857>`_ CitrixResourceBase wrongly calculates total memory on hosts with a lot of memory...
+`CLOUDSTACK-7853 <https://issues.apache.org/jira/browse/CLOUDSTACK-7853>`_ Hosts that are temporary Disconnected and get behind on ping (PingTimeout) turn ...
+`CLOUDSTACK-7839 <https://issues.apache.org/jira/browse/CLOUDSTACK-7839>`_ Unable to live migrate an instance to another host in a cluster from which the t...
+`CLOUDSTACK-7827 <https://issues.apache.org/jira/browse/CLOUDSTACK-7827>`_ storage migration timeout, loss of data...
+`CLOUDSTACK-7819 <https://issues.apache.org/jira/browse/CLOUDSTACK-7819>`_ Cannot add tags to project...
+`CLOUDSTACK-7813 <https://issues.apache.org/jira/browse/CLOUDSTACK-7813>`_ Management server is stuck after upgrade from 4.4.0 to 4.4.1...
+`CLOUDSTACK-7807 <https://issues.apache.org/jira/browse/CLOUDSTACK-7807>`_ Allow rate limiting on VPC public interface only...
+`CLOUDSTACK-7790 <https://issues.apache.org/jira/browse/CLOUDSTACK-7790>`_ VXLAN interface MTU change from 1450 to 1500 and JUMBRO frames...
+`CLOUDSTACK-7789 <https://issues.apache.org/jira/browse/CLOUDSTACK-7789>`_ I was updated from version 4.4.0 of Apache CloudStack to 4.4.1. It does not work...
+`CLOUDSTACK-7782 <https://issues.apache.org/jira/browse/CLOUDSTACK-7782>`_ The 4.4.1 web UI is missing "Acquire new IP address" buton in NIC section...
+`CLOUDSTACK-7781 <https://issues.apache.org/jira/browse/CLOUDSTACK-7781>`_ Typo in calling /opt/cloud/bin/createipAlias.sh...
+`CLOUDSTACK-7751 <https://issues.apache.org/jira/browse/CLOUDSTACK-7751>`_ Autoscaling without netscaler...
+`CLOUDSTACK-7750 <https://issues.apache.org/jira/browse/CLOUDSTACK-7750>`_ Xen server can not mount secondary CIFS storage...
+`CLOUDSTACK-7656 <https://issues.apache.org/jira/browse/CLOUDSTACK-7656>`_ Secondary Storage VM fails to download templates served by Varnish HTTP cache...
+`CLOUDSTACK-7640 <https://issues.apache.org/jira/browse/CLOUDSTACK-7640>`_ Failed to delete template that failed to download...
+`CLOUDSTACK-7578 <https://issues.apache.org/jira/browse/CLOUDSTACK-7578>`_ XenServerInvestigator should do better investigation in case of OVS or other net...
+`CLOUDSTACK-7449 <https://issues.apache.org/jira/browse/CLOUDSTACK-7449>`_ "CloudRuntimeException: Can not see storage pool" after trying to add a new host...
+`CLOUDSTACK-7443 <https://issues.apache.org/jira/browse/CLOUDSTACK-7443>`_ Cannot launch SSVMs when using Swift as Secondary Storage...
+`CLOUDSTACK-7406 <https://issues.apache.org/jira/browse/CLOUDSTACK-7406>`_ Templates using Swift provider reports physical size, and not the virtual size i...
+`CLOUDSTACK-7365 <https://issues.apache.org/jira/browse/CLOUDSTACK-7365>`_ Upgrading without proper systemvm template corrupt cloudstack management server...
+`CLOUDSTACK-7342 <https://issues.apache.org/jira/browse/CLOUDSTACK-7342>`_ Fail to delete template while using Swift as Secondary Storage...
+`CLOUDSTACK-7341 <https://issues.apache.org/jira/browse/CLOUDSTACK-7341>`_ Snapshot not allowed for hypervisor KVM...
+========================================================================== ===================================================================================
+
+
+All known issues
+-----------------
+
For the list of known issues, see `Known Issues in
-<https://issues.apache.org/jira/issues/?filter=12328007>`_ |release|.
+<https://issues.apache.org/jira/issues/?filter=12328007>`_ |version|.
========================================================================== ===================================================================================
Bug ID Description
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/upgrade/upgrade-4.4.0.rst
----------------------------------------------------------------------
diff --git a/source/upgrade/upgrade-4.4.0.rst b/source/upgrade/upgrade-4.4.0.rst
new file mode 100644
index 0000000..22a1a3d
--- /dev/null
+++ b/source/upgrade/upgrade-4.4.0.rst
@@ -0,0 +1,380 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information#
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+
+.. |version_to_upgrade| replace:: 4.4.0
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+
+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.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+
+#. Upgrade CloudStack management server(s)
+
+#. Update hypervisors specific dependencies
+
+
+Packages repository
+-------------------
+
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack 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 |version| 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 :ref:`ubuntu43` or :ref:`rhel43` and :ref:`kvm43` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+
+Database Preparation
+--------------------
+
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-usage stop
+
+#. 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.
+
+ .. sourcecode:: bash
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. sourcecode:: bash
+
+ $ 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:
+
+ .. sourcecode:: bash
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu44:
+
+Management Server on Ubuntu
+---------------------------
+
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel44`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. 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 CloudStack 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.)
+
+
+.. _apt-repo44:
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+#. Update your apt package list:
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel44:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section, then :ref:`upg-sysvm44`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+
+.. _rpm-repo44:
+
+CloustStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. sourcecode:: bash
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. sourcecode:: bash
+
+ $ sudo yum upgrade cloudstack-usage
+
+
+hypervisor: XenServer
+---------------------
+
+ **(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+ Copy the file `vhd-utils <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_
+ to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+ .. sourcecode:: bash
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloud.com.s3.amazonaws.com/tools/vhd-util
+
+
+hypervisor: VMware
+------------------
+
+ .. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to `Building from Source
+ <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/building_from_source.html>`_.
+
+ **(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:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. sourcecode:: bash
+
+ $ 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:
+
+ .. sourcecode:: bash
+
+ $ mysql -u <username> -p<password>
+
+ .. sourcecode:: bash
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. sourcecode:: bash
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. sourcecode:: bash
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. sourcecode:: bash
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. sourcecode:: bash
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. sourcecode:: bash
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm44:
+
+hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(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.
+
+#. Configure the :ref:`apt-repo44` as detailed above.
+
+#. Stop the running agent.
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. sourcecode:: bash
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo44` as detailed above.
+
+ .. sourcecode:: bash
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. sourcecode:: bash
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. If upgrading fresh installation of 4.4.0
+
+ If you are upgrading fresh installation of CloudStack 4.4.0, the following MySQL
+ command must be executed before restarting the management server. If the system
+ was running pre 4.4 and then upgraded to 4.4.0, the MySQL command is not required.
+ Refer to: `CLOUDSTACK-7813 <https://issues.apache.org/jira/browse/CLOUDSTACK-7813>`_
+
+ .. sourcecode:: mysql
+
+ use cloud;
+ ALTER TABLE `snapshot_policy` ADD `display` TINYINT( 1 ) NOT NULL DEFAULT '1';
+
+#. Now it's time to start the management server
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-usage start
+
+
+.. _upg-sysvm44:
+
+System-VMs and Virtual-Routers
+------------------------------
+
+.. include:: _sysvm_restart.rst
+
+
+.. include:: /global.rst
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/upgrade/upgrade-4.4.1.rst
----------------------------------------------------------------------
diff --git a/source/upgrade/upgrade-4.4.1.rst b/source/upgrade/upgrade-4.4.1.rst
new file mode 100644
index 0000000..f8bdbe4
--- /dev/null
+++ b/source/upgrade/upgrade-4.4.1.rst
@@ -0,0 +1,358 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information#
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+
+.. |version_to_upgrade| replace:: 4.4.1
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+
+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.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+
+#. Upgrade CloudStack management server(s)
+
+#. Update hypervisors specific dependencies
+
+
+Packages repository
+-------------------
+
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack 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 |version| 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 :ref:`ubuntu43` or :ref:`rhel43` and :ref:`kvm43` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+
+Database Preparation
+--------------------
+
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-usage stop
+
+#. 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.
+
+ .. sourcecode:: bash
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. sourcecode:: bash
+
+ $ 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:
+
+ .. sourcecode:: bash
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu44:
+
+Management Server on Ubuntu
+---------------------------
+
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel44`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. 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 CloudStack 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.)
+
+
+.. _apt-repo44:
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+#. Update your apt package list:
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel44:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section, then :ref:`upg-sysvm44`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+
+.. _rpm-repo44:
+
+CloustStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. sourcecode:: bash
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. sourcecode:: bash
+
+ $ sudo yum upgrade cloudstack-usage
+
+
+hypervisor: XenServer
+---------------------
+
+ **(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+ Copy the file `vhd-utils <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_
+ to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+ .. sourcecode:: bash
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloud.com.s3.amazonaws.com/tools/vhd-util
+
+
+hypervisor: VMware
+------------------
+
+ .. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to `Building from Source
+ <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/building_from_source.html>`_.
+
+ **(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:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. sourcecode:: bash
+
+ $ 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:
+
+ .. sourcecode:: bash
+
+ $ mysql -u <username> -p<password>
+
+ .. sourcecode:: bash
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. sourcecode:: bash
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. sourcecode:: bash
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. sourcecode:: bash
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. sourcecode:: bash
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. sourcecode:: bash
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm44:
+
+hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(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.
+
+#. Configure the :ref:`apt-repo44` as detailed above.
+
+#. Stop the running agent.
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. sourcecode:: bash
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. sourcecode:: bash
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo44` as detailed above.
+
+ .. sourcecode:: bash
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. sourcecode:: bash
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. sourcecode:: bash
+
+ $ sudo service cloudstack-usage start
+
+
+.. include:: /global.rst
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/5ab48e4c/source/upgrade/upgrade-4.4.rst
----------------------------------------------------------------------
diff --git a/source/upgrade/upgrade-4.4.rst b/source/upgrade/upgrade-4.4.rst
deleted file mode 100644
index 22a1a3d..0000000
--- a/source/upgrade/upgrade-4.4.rst
+++ /dev/null
@@ -1,380 +0,0 @@
-.. Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information#
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
-
-
-.. |version_to_upgrade| replace:: 4.4.0
-
-Upgrade Instruction from |version_to_upgrade|
-=============================================
-
-
-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.
-
-.. note::
- The following upgrade instructions should be performed regardless of
- hypervisor type.
-
-Upgrade Steps:
-
-#. Backup CloudStack database (MySQL)
-
-#. Upgrade CloudStack management server(s)
-
-#. Update hypervisors specific dependencies
-
-
-Packages repository
--------------------
-
-
-Most users of CloudStack manage the installation and upgrades of
-CloudStack 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 |version| 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 :ref:`ubuntu43` or :ref:`rhel43` and :ref:`kvm43` hosts upgrade.
-
-Instructions for creating packages from the CloudStack source are in the
-`CloudStack Installation Guide`_.
-
-.. include:: _sysvm_templates.rst
-
-
-Database Preparation
---------------------
-
-
-Backup current database
-
-#. Stop your management server or servers. Run this on all management
- server hosts:
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-management stop
-
-#. If you are running a usage server or usage servers, stop those as well:
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-usage stop
-
-#. 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.
-
- .. sourcecode:: bash
-
- $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
- $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
-
-#. **(KVM Only)** If primary storage of type local storage is in use, the
- path for this storage needs to be verified to ensure it passes new
- validation. Check local storage by querying the cloud.storage\_pool
- table:
-
- .. sourcecode:: bash
-
- $ 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:
-
- .. sourcecode:: bash
-
- $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
-
-
-.. _ubuntu44:
-
-Management Server on Ubuntu
----------------------------
-
-
-If you are using Ubuntu, follow this procedure to upgrade your packages. If
-not, skip to step :ref:`rhel44`.
-
-.. note::
- **Community Packages:** This section assumes you're using the community
- supplied packages for CloudStack. 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 CloudStack 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.)
-
-
-.. _apt-repo44:
-
-CloudStack apt repository
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-
-#. Update your apt package list:
-
- .. sourcecode:: bash
-
- $ sudo apt-get update
-
-#. Now that you have the repository configured, it's time to upgrade
- the ``cloudstack-management`` package.
-
- .. sourcecode:: bash
-
- $ sudo apt-get upgrade cloudstack-management
-
-#. If you use CloudStack usage server
-
- .. sourcecode:: bash
-
- $ sudo apt-get upgrade cloudstack-usage
-
-
-.. _rhel44:
-
-Management Server on CentOS/RHEL
---------------------------------
-
-If you are using CentOS or RHEL, follow this procedure to upgrade your
-packages. If not, skip to hypervisors section, then :ref:`upg-sysvm44`.
-
-.. note::
- **Community Packages:** This section assumes you're using the community
- supplied packages for CloudStack. If you've created your own packages and
- yum repository, substitute your own URL for the ones used in these examples.
-
-
-.. _rpm-repo44:
-
-CloustStack RPM repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-
-#. Now that you have the repository configured, it's time to upgrade the
- ``cloudstack-management``.
-
- .. sourcecode:: bash
-
- $ sudo yum upgrade cloudstack-management
-
-#. If you use CloudStack usage server
-
- .. sourcecode:: bash
-
- $ sudo yum upgrade cloudstack-usage
-
-
-hypervisor: XenServer
----------------------
-
- **(XenServer only)** Copy vhd-utils file on CloudStack management servers.
- Copy the file `vhd-utils <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_
- to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
-
- .. sourcecode:: bash
-
- wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
- http://download.cloud.com.s3.amazonaws.com/tools/vhd-util
-
-
-hypervisor: VMware
-------------------
-
- .. warning::
- For VMware hypervisor CloudStack management server packages must be
- build using "noredist". Refer to `Building from Source
- <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/building_from_source.html>`_.
-
- **(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:
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-management stop
-
-#. Generate the encrypted equivalent of your vCenter password:
-
- .. sourcecode:: bash
-
- $ 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:
-
- .. sourcecode:: bash
-
- $ mysql -u <username> -p<password>
-
- .. sourcecode:: bash
-
- select * from cloud.cluster_details;
-
-#. Update the plain text password with the encrypted one
-
- .. sourcecode:: bash
-
- update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_;
-
-#. Confirm that the table is updated:
-
- .. sourcecode:: bash
-
- select * from cloud.cluster_details;
-
-#. Find the ID of the correct row of vmware\_data\_center that you
- want to update
-
- .. sourcecode:: bash
-
- select * from cloud.vmware_data_center;
-
-#. update the plain text password with the encrypted one:
-
- .. sourcecode:: bash
-
- update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_;
-
-#. Confirm that the table is updated:
-
- .. sourcecode:: bash
-
- select * from cloud.vmware_data_center;
-
-
-.. _kvm44:
-
-hypervisor: KVM
----------------
-
-KVM on Ubuntu
-^^^^^^^^^^^^^
-
-(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.
-
-#. Configure the :ref:`apt-repo44` as detailed above.
-
-#. Stop the running agent.
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-agent stop
-
-#. Update the agent software.
-
- .. sourcecode:: bash
-
- $ sudo apt-get upgrade cloudstack-agent
-
-#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
- line that reads:
-
- .. sourcecode:: bash
-
- paths.script=/usr/share/cloudstack-common
-
- If not, add the line.
-
-#. Start the agent.
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-agent start
-
-
-KVM on CentOS/RHEL
-^^^^^^^^^^^^^^^^^^
-For KVM hosts, upgrade the ``cloudstack-agent`` package
-
-#. Configure the :ref:`rpm-repo44` as detailed above.
-
- .. sourcecode:: bash
-
- $ sudo yum upgrade cloudstack-agent
-
-#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
- line that reads:
-
- .. sourcecode:: bash
-
- paths.script=/usr/share/cloudstack-common
-
- If not, add the line.
-
-#. Restart the agent:
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-agent stop
- $ sudo killall jsvc
- $ sudo service cloudstack-agent start
-
-
-Restart management services
----------------------------
-
-#. If upgrading fresh installation of 4.4.0
-
- If you are upgrading fresh installation of CloudStack 4.4.0, the following MySQL
- command must be executed before restarting the management server. If the system
- was running pre 4.4 and then upgraded to 4.4.0, the MySQL command is not required.
- Refer to: `CLOUDSTACK-7813 <https://issues.apache.org/jira/browse/CLOUDSTACK-7813>`_
-
- .. sourcecode:: mysql
-
- use cloud;
- ALTER TABLE `snapshot_policy` ADD `display` TINYINT( 1 ) NOT NULL DEFAULT '1';
-
-#. Now it's time to start the management server
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-management start
-
-#. If you use it, start the usage server
-
- .. sourcecode:: bash
-
- $ sudo service cloudstack-usage start
-
-
-.. _upg-sysvm44:
-
-System-VMs and Virtual-Routers
-------------------------------
-
-.. include:: _sysvm_restart.rst
-
-
-.. include:: /global.rst