You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ke...@apache.org on 2012/12/15 07:18:39 UTC
[2/2] updating release notes for 4.0.1
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/095f5523/docs/en-US/Release_Notes.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml
index 849dc5a..b081870 100644
--- a/docs/en-US/Release_Notes.xml
+++ b/docs/en-US/Release_Notes.xml
@@ -19,7 +19,7 @@
under the License.
-->
<book>
- <xi:include href="Book_Info_Release_Notes_4.0.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="Book_Info_Release_Notes_4-0.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
<chapter id="submitting-feedback">
<title>Submitting Feedback and Getting Help</title>
<para>The Apache CloudStack project has mailing lists for users and developers. These are the
@@ -32,16 +32,128 @@
Anyone contributing to CloudStack should be on this mailing list.</para>
<para>You can also report bugs in CloudStack using the <ulink
url="https://issues.apache.org/jira/secure/CreateIssue!default.jspa">Apache Defect Tracking
- System</ulink></para>
+ System</ulink>.</para>
<para>To posts to the lists, you'll need to be subscribed. See the <ulink
url="http://incubator.apache.org/cloudstack/mailing-lists.html">CloudStack Web site</ulink>
for instructions.</para>
</chapter>
<chapter id="upgrade-instructions">
<title>Upgrade Instructions</title>
- <section id="upgrade-from-3.0.2-to-4.0">
- <title>Upgrade from 3.0.2 to 4.0.0-incubating</title>
- <para>Perform the following to upgrade from version 3.0.2 to version 4.0.0-incubating. Note
+ <section id="upgrade-from-4.0.0-to-4.0.1">
+ <title>Upgrade from 4.0.0-incubating to 4.0.1-incubating</title>
+ <para>Perform the following to upgrade from version 4.0.0-incubating to version
+ 4.0.1 incubating. Note that some of the steps here are only required if you're using
+ a specific hypervisor. The steps that are hypervisor-specific are called out with a note.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>Stop all Usage Servers if running. Run this on all Usage Server hosts.</para>
+ <programlisting># service cloud-usage stop</programlisting>
+ </listitem>
+ <listitem>
+ <para>Stop the Management Servers. Run this on all Management Server hosts.</para>
+ <programlisting># service cloud-management stop</programlisting>
+ </listitem>
+ <listitem>
+ <para>On the MySQL master, take a backup of the MySQL databases. We recommend performing
+ this step even in test upgrades. If there is an issue, this will assist with
+ debugging.</para>
+ <para>In the following commands, it is assumed that you have set the root password on the
+ database, which is a CloudStack recommended best practice. Substitute your own MySQL
+ root password.</para>
+ <programlisting><prompt>#</prompt> <command>mysqldump</command> -u root -p<replaceable>mysql_password</replaceable> cloud > <filename>cloudstack_backup.dmp</filename>
+<prompt>#</prompt> <command>mysqldump</command> -u root -p<replaceable>mysql_password</replaceable> cloud_usage > <filename>usage_backup.dmp</filename></programlisting>
+ </listitem>
+ <listitem>
+ <para>Either build RPM/DEB packages as detailed in the Installation Guide, or use one of
+ the community provided yum/apt repositories to gain access to the &PRODUCT;
+ binaries.</para>
+ </listitem>
+ <listitem>
+ <para>After you have configured an appropriate yum or apt repository, you may execute the
+ one of the following commands as appropriate for your environment in order to upgrade
+ &PRODUCT;: <programlisting><prompt>#</prompt> <command>yum</command> update cloud-*</programlisting>
+ <programlisting><prompt>#</prompt> <command>apt-get</command> update
+<prompt>#</prompt> <command>apt-get</command> upgrade cloud-*</programlisting>
+ </para>
+ <para>You will, of course, have to agree to the changes suggested by Yum or APT.</para>
+ <note>
+ <para>If you have more than one management server node, repeat the upgrade steps on each
+ node.</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>Start the first Management Server. Do not start any other Management Server nodes
+ yet.</para>
+ <programlisting># service cloud-management start</programlisting>
+ <para>Wait until the databases are upgraded. Ensure that the database upgrade is complete.
+ After confirmation, start the other Management Servers one at a time by running the same
+ command on each node.</para>
+ <note>
+ <para>Failing to restart the Management Server indicates a problem in the upgrade.
+ Having the Management Server restarted without any issues indicates that the upgrade
+ is successfully completed.</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>Start all Usage Servers (if they were running on your previous version). Perform
+ this on each Usage Server host.</para>
+ <para><command># service cloud-usage start</command></para>
+ </listitem>
+ <listitem>
+ <note>
+ <para>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.</para>
+ </note>
+ <orderedlist numeration="loweralpha">
+ <listitem>
+ <para>Configure a yum or apt respository containing the &PRODUCT; packages as outlined
+ in the Installation Guide.</para>
+ </listitem>
+ <listitem>
+ <para>Stop the running agent.</para>
+ <para><command># service cloud-agent stop</command></para>
+ </listitem>
+ <listitem>
+ <para>Update the agent software with one of the following command sets as appropriate
+ for your environment.</para>
+ <para><command># yum update cloud-*</command></para>
+ <para><command># apt-get update</command></para>
+ <para><command># apt-get upgrade cloud-*</command></para>
+ </listitem>
+ <listitem>
+ <para>Start the agent.</para>
+ <programlisting># service cloud-agent start</programlisting>
+ </listitem>
+ <listitem>
+ <para>Edit <filename>/etc/cloud/agent/agent.properties</filename> to change the
+ resource parameter from
+ "com.cloud.agent.resource.computing.LibvirtComputingResource" to
+ "com.cloud.hypervisor.kvm.resource.LibvirtComputingResource".</para>
+ </listitem>
+ <listitem>
+ <para>When the Management Server is up and running, log in to the CloudStack UI and
+ restart the virtual router for proper functioning of all the features.</para>
+ </listitem>
+ </orderedlist>
+ </listitem>
+ <listitem>
+ <para>Log in to the CloudStack UI as administrator, and check the status of the hosts. All
+ hosts should come to Up state (except those that you know to be offline). You may need
+ to wait 20 or 30 minutes, depending on the number of hosts.</para>
+ <note>
+ <para>Troubleshooting: If login fails, clear your browser cache and reload the
+ page.</para>
+ </note>
+ <para/>
+ <para>Do not proceed to the next step until the hosts show in Up state.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="upgrade-from-3.0.2-to-4.0.1">
+ <title>Upgrade from 3.0.2 to 4.0.1-incubating</title>
+ <para>Perform the following to upgrade from version 3.0.2 to version 4.0.1-incubating. Note
that some of the steps here are only required if you're using a specific hypervisor. The
steps that are hypervisor-specific are called out with a note.</para>
<orderedlist>
@@ -92,11 +204,11 @@
<tbody>
<row>
<entry><para>Name</para></entry>
- <entry><para>systemvm-vmware-3.0.5</para></entry>
+ <entry><para>systemvm-vmware-3.0.0</para></entry>
</row>
<row>
<entry><para>Description</para></entry>
- <entry><para>systemvm-vmware-3.0.5</para></entry>
+ <entry><para>systemvm-vmware-3.0.0</para></entry>
</row>
<row>
<entry><para>URL</para></entry>
@@ -174,6 +286,7 @@
<programlisting><prompt>#</prompt> <command>apt-get</command> update
<prompt>#</prompt> <command>apt-get</command> upgrade cloud-*</programlisting>
</para>
+ <para>You will, of course, have to agree to the changes suggested by Yum or APT.</para>
<note>
<para>If the upgrade output includes a message similar to the following, then some
custom content was found in your old components.xml, and you need to merge the two
@@ -187,7 +300,7 @@
<filename>/etc/cloud/management/components.xml</filename> the changes will be
preserved in the upgrade. However, you need to do the following steps to place these
changes in a new version of the file which is compatible with version
- 4.0.0-incubating.</para>
+ 4.0.1-incubating.</para>
<orderedlist numeration="loweralpha">
<listitem>
<para>Make a backup copy of <filename>/etc/cloud/management/components.xml</filename>.
@@ -314,8 +427,8 @@
</listitem>
<listitem>
<para>If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a version
- supported by CloudStack 4.0.0-incubating. The supported versions are XenServer 5.6 SP2
- and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.0.0-incubating
+ supported by CloudStack 4.0.1-incubating. The supported versions are XenServer 5.6 SP2
+ and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.0.1-incubating
Installation Guide.</para>
</listitem>
<listitem>
@@ -471,7 +584,7 @@
</note>
</section>
<section id="upgrade-from-2.2.x-to-4.0">
- <title>Upgrade from 2.2.14 to 4.0.0-incubating</title>
+ <title>Upgrade from 2.2.14 to 4.0.1-incubating</title>
<orderedlist>
<listitem>
<para>Ensure that you query your IPaddress usage records and process them; for example,
@@ -479,7 +592,7 @@
<para>Starting in 3.0.2, the usage record format for IP addresses is the same as the rest
of the usage types. Instead of a single record with the assignment and release dates,
separate records are generated per aggregation period with start and end dates. After
- upgrading to 4.0.0-incubating, any existing IP address usage records in the old format
+ upgrading to 4.0.1-incubating, any existing IP address usage records in the old format
will no longer be available.</para>
</listitem>
<listitem>
@@ -490,7 +603,7 @@
<para>If KVM hypervisor is used in your cloud, be sure you completed the step to insert
a valid username and password into the host_details table on each KVM node as
described in the 2.2.14 Release Notes. This step is critical, as the database will be
- encrypted after the upgrade to 4.0.0-incubating.</para>
+ encrypted after the upgrade to 4.0.1-incubating.</para>
</warning>
</listitem>
<listitem>
@@ -559,8 +672,8 @@
</row>
<row>
<entry><para>VMware</para></entry>
- <entry><para>Name: systemvm-vmware-3.0.5</para>
- <para>Description: systemvm-vmware-3.0.5</para>
+ <entry><para>Name: systemvm-vmware-3.0.0</para>
+ <para>Description: systemvm-vmware-3.0.0</para>
<para>URL:
http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova</para>
<para>Zone: Choose the zone where this hypervisor is used</para>
@@ -619,12 +732,13 @@
<programlisting><prompt>#</prompt> <command>apt-get</command> update
<prompt>#</prompt> <command>apt-get</command> upgrade cloud-*</programlisting>
</para>
+ <para>You will, of course, have to agree to the changes suggested by Yum or APT.</para>
</listitem>
<listitem>
<para>If you have made changes to your existing copy of the file components.xml in your
previous-version CloudStack installation, the changes will be preserved in the upgrade.
However, you need to do the following steps to place these changes in a new version of
- the file which is compatible with version 4.0.0-incubating.</para>
+ the file which is compatible with version 4.0.1-incubating.</para>
<note>
<para>How will you know whether you need to do this? If the upgrade output in the
previous step included a message like the following, then some custom content was
@@ -655,7 +769,7 @@
<filename>/etc/cloud/management/db.properties</filename> file in your previous-version
CloudStack installation, the changes will be preserved in the upgrade. However, you need
to do the following steps to place these changes in a new version of the file which is
- compatible with version 4.0.0-incubating.</para>
+ compatible with version 4.0.1-incubating.</para>
<orderedlist>
<listitem>
<para>Make a backup copy of your file
@@ -806,7 +920,7 @@ Done restarting router(s).
<programlisting><prompt>#</prompt> <command>ssh</command> -i <replaceable>private-key-path</replaceable> <replaceable>link-local-ip</replaceable> -p 3922
# cat /etc/cloudstack-release</programlisting>
<para>The output should be like the following:</para>
- <programlisting>Cloudstack Release 4.0.0-incubating Mon Oct 9 15:10:04 PST 2012</programlisting>
+ <programlisting>Cloudstack Release 4.0.1-incubating Mon Oct 9 15:10:04 PST 2012</programlisting>
<formalpara>
<title>ESXi</title>
<para>SSH in using the private IP address of the system VM. For example, in the command
@@ -818,12 +932,12 @@ Done restarting router(s).
<prompt>#</prompt> <command>cat</command> <filename>/etc/cloudstack-release</filename>
</programlisting>
<para>The output should be like the following:</para>
- <programlisting>Cloudstack Release 4.0.0-incubating Mon Oct 9 15:10:04 PST 2012</programlisting>
+ <programlisting>Cloudstack Release 4.0.1-incubating Mon Oct 9 15:10:04 PST 2012</programlisting>
</listitem>
<listitem>
<para>If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a version
- supported by CloudStack 4.0.0-incubating. The supported versions are XenServer 5.6 SP2
- and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.0.0-incubating
+ supported by CloudStack 4.0.1-incubating. The supported versions are XenServer 5.6 SP2
+ and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.0.1-incubating
Installation Guide.</para>
</listitem>
<listitem>
@@ -978,359 +1092,14 @@ Done restarting router(s).
</section>
</chapter>
<chapter id="version-4.0">
- <title>Version 4.0.0-incubating</title>
+ <title>Version 4.0.1-incubating</title>
<section id="what-new-in-4.0">
- <title>What’s New in 4.0.0-incubating</title>
- <para>Apache CloudStack 4.0.0-incubating includes the following new features:</para>
- <section id="inter-vlan-routing">
- <title>Inter-VLAN Routing</title>
- <para>Inter-VLAN Routing is the capability to route network traffic between VLANs. This
- feature enables you to set up Virtual Private Clouds (VPC) that can hold multi-tier
- applications. These tiers are deployed on different VLANs that can communicate with each
- other. You can provision VLANs to the tiers your create, and VMs can be deployed on
- different tiers, such as Web, Application, or Database. The VLANs are connected to a
- virtual router, which facilitates communication between the VMs. In effect, you can
- segment VMs by means of VLANs into different networks that can host multi-tier
- applications. Such segmentation by means of VLANs logically separate application VMs for
- higher security and lower broadcasts, while remaining physically connected to the same
- device.</para>
- <para>This feature is supported on XenServer and VMware hypervisors.</para>
- </section>
- <section id="site-to-site-vpn">
- <title>Site-to-Site VPN</title>
- <para>A Site-to-Site VPN connection helps you establish a secure connection from an
- enterprise datacenter to the cloud infrastructure. This allows users to access the guest
- VMs by establishing a VPN connection to the virtual router of the account from a device in
- the datacenter of the enterprise. Having this facility eliminates the need to establish
- VPN connections to individual VMs.</para>
- <para>The supported endpoints on the remote datacenters are:</para>
- <itemizedlist>
- <listitem>
- <para>Cisco ISR with IOS 12.4 or later</para>
- </listitem>
- <listitem>
- <para>Juniper J-Series routers with JunOS 9.5 or later</para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="local-storage-support">
- <title>Local Storage Support for Data Volumes</title>
- <para>You can now create data volumes on local storage. The data volume is placed on the
- same XenServer host as the VM instance that is attached to the data volume. These local
- data volumes can be attached to virtual machines, detached, re-attached, and deleted just
- as with the other types of data volume. In earlier releases of CloudStack, only the root
- disk could be placed in local storage.</para>
- <para>Local storage is ideal for scenarios where persistence of data volumes and HA is not
- required. Some of the benefits include reduced disk I/O latency and cost reduction from
- using inexpensive local disks.</para>
- <para>In order for local volumes to be used, the feature must be enabled for the
- zone.</para>
- <para>You can create a data disk offering for local storage. When a user creates a new VM,
- they can select this disk offering in order to cause the data disk volume to be placed in
- local storage.</para>
- <para>You can not migrate a VM that has a volume in local storage to a different host, nor
- migrate the volume itself away to a different host. If you want to put a host into
- maintenance mode, you must first stop any VMs with local data volumes on that host.</para>
- <para>Local storage support for volumes is available for XenServer, KVM, and VMware
- hypervisors.</para>
- </section>
- <section id="tags">
- <title>Tags</title>
- <para>A tag is a key-value pair that stores metadata about a resource in the cloud. Tags are
- useful for categorizing resources. For example, you can tag a user VM with a value that
- indicates the user's city of residence. In this case, the key would be "city" and the
- value might be "Toronto" or "Tokyo." You can then request CloudStack to find all resources
- that have a given tag; for example, VMs for users in a given city.</para>
- <para>You can tag a user virtual machine, volume, snapshot, guest network, template, ISO,
- firewall rule, port forwarding rule, public IP address, security group, load balancer
- rule, project, VPC, network ACL, or static route. You can not tag a remote access
- VPN.</para>
- <para>You can work with tags through the UI or through the new API commands createTags,
- deleteTags, and listTags. You can define multiple tags for each resource. There is no
- limit on the number of tags you can define. Each tag can be up to 255 characters long.
- Users can define tags on the resources they own, and administrators can define tags on any
- resources in the cloud.</para>
- <para>A new optional input parameter, "tags," has been added to many of the list* API
- commands. The following example shows how to use this new parameter to find all the
- volumes having tag region=canada OR tag city=Toronto:</para>
- <programlisting>command=listVolumes
-&listAll=true
-&tags[0].key=region
-&tags[0].value=canada
-&tags[1].key=city
-&tags[1].value=Toronto</programlisting>
- <para>The following API commands have the new "tags" input parameter:</para>
- <itemizedlist>
- <listitem>
- <para>listVirtualMachines</para>
- </listitem>
- <listitem>
- <para>listVolumes</para>
- </listitem>
- <listitem>
- <para>listSnapshots</para>
- </listitem>
- <listitem>
- <para>listNetworks</para>
- </listitem>
- <listitem>
- <para>listTemplates</para>
- </listitem>
- <listitem>
- <para>listIsos</para>
- </listitem>
- <listitem>
- <para>listFirewallRules</para>
- </listitem>
- <listitem>
- <para>listPortForwardingRules</para>
- </listitem>
- <listitem>
- <para>listPublicIpAddresses</para>
- </listitem>
- <listitem>
- <para>listSecurityGroups</para>
- </listitem>
- <listitem>
- <para>listLoadBalancerRules</para>
- </listitem>
- <listitem>
- <para>listProjects</para>
- </listitem>
- <listitem>
- <para>listVPCs</para>
- </listitem>
- <listitem>
- <para>listNetworkACLs</para>
- </listitem>
- <listitem>
- <para>listStaticRoutes</para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="aws-tags">
- <title>AWS API Changes for Tags</title>
- <para>Some changes have been made to the Amazon Web Services API compatibility support in
- order to accommodate the new tagging feature.</para>
- <para>New APIs:</para>
- <informaltable>
- <tgroup cols="2" align="left" colsep="1" rowsep="1">
- <colspec colwidth="1.0*" colname="1" colnum="1"/>
- <colspec colwidth="4.3*" colname="2" colnum="2"/>
- <thead>
- <row>
- <entry>
- <para>New API</para>
- </entry>
- <entry>
- <para>Description</para>
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <para>ec2-create-tags </para>
- </entry>
- <entry>
- <para>Add tags to one or more resources.</para>
- </entry>
- </row>
- <row>
- <entry>
- <para>ec2-delete-tags</para>
- </entry>
- <entry>
- <para>Remove tags from one or more resources.</para>
- </entry>
- </row>
- <row>
- <entry>ec2-describe-tags</entry>
- <entry>
- <para>Show currently defined tags.</para>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- <para>Changed APIs:</para>
- <informaltable>
- <tgroup cols="2" align="left" colsep="1" rowsep="1">
- <colspec colwidth="1" colname="1" colnum="1"/>
- <colspec colwidth="2*" colname="2" colnum="2"/>
- <thead>
- <row>
- <entry>
- <para>Changed API</para>
- </entry>
- <entry>
- <para>Description</para>
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>ec2-describe-images</entry>
- <entry>
- <para>Output now shows tags defined for each image.</para>
- </entry>
- </row>
- <row>
- <entry>
- <para>ec2-describe-instances </para>
- </entry>
- <entry>
- <para>Output now shows tags defined for each image.</para>
- <para>The following filters can now be passed in to limit the output result set:
- tag-key, tag-value and tag:key</para>
- </entry>
- </row>
- <row>
- <entry>
- <para>ec2-describe-snapshots</para>
- </entry>
- <entry>
- <para>Output now shows tags defined for each image.</para>
- <para>The following filters can now be passed in to limit the output result set:
- tag-key, tag-value and tag:key</para>
- </entry>
- </row>
- <row>
- <entry>ec2-describe-volumes</entry>
- <entry>
- <para>Output now shows tags defined for each image.</para>
- <para>The following filters can now be passed in to limit the output result set:
- tag-key, tag-value and tag:key</para>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- </section>
- <section id="secure-console-access-on-xenserver">
- <title>Secure Console Access on XenServer</title>
- <para>With the addition of Secure Console feature, users can now securely access the VM
- consoles on the XenServer hypervisor. You can either SSH or use the View Console option in
- the Management Server to securely connect to the VMs on the XenServer host. The Management
- Server uses the xapi API to stream the VM consoles. However, there is no change in the way
- you can access the console of a VM. This feature is supported on XenServer 5.6 and 6.0
- versions.</para>
- </section>
- <section id="release-note-stopped-vm">
- <title>Stopped VM</title>
- <para>This release supports creating VMs without starting them on the backend. You can
- determine whether the VM needs to be started as part of the VM deployment. A VM can be
- deployed in two ways: create and start a VM (the default method); create a VM and leave it
- in the stopped state.</para>
- <para>A new request parameter, startVM, is introduced in the deployVm API to support the
- stopped VM feature. The possible values are:</para>
- <itemizedlist>
- <listitem>
- <para>true - The VM starts as a part of the VM deployment</para>
- </listitem>
- <listitem>
- <para>false - The VM is left in stopped state at the end of the VM deployment</para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="release-note-upload-existing-volume-to-vm">
- <title>Uploading an Existing Volume to a Virtual Machine</title>
- <para>Existing data can now be made accessible to a virtual machine. This is called
- uploading a volume to the VM. For example, this is useful to upload data from a local file
- system and attach it to a VM. Root administrators, domain administrators, and end users
- can all upload existing volumes to VMs. The upload is performed by using HTTP. The
- uploaded volume is placed in the zone's secondary storage.</para>
- <para>This functionality is supported for the following hypervisors:</para>
- <itemizedlist>
- <listitem>
- <para>Hypervisor : Disk Image Format</para>
- </listitem>
- <listitem>
- <para>XenServer : VHD</para>
- </listitem>
- <listitem>
- <para>VMware : OVA</para>
- </listitem>
- <listitem>
- <para>KVM : QCOW2</para>
- </listitem>
- <!-- <listitem>
- <para>OVM : RAW</para>
- </listitem> -->
- </itemizedlist>
- </section>
- <section id="dedicated-ha-hosts">
- <title>Dedicated High-Availability Hosts</title>
- <para>One or more hosts can now be designated for use only by high-availability (HA) enabled
- VMs that are restarted due to a host failure. Setting up a pool of such dedicated HA hosts
- as the recovery destination for all HA-enabled VMs make it easier to determine which VMs
- are restarted as part of the high-availability function. You can designate a host as a
- dedicated-HA restart node only if the Dedicated HA Hosts feature is enabled by setting the
- appropriate global configuration parameter.</para>
- </section>
- <section id="support-for-aws-api">
- <title>Support for Amazon Web Services API</title>
- <para>This release supports Amazon Web Services APIs, including Elastic Compute Cloud (EC2)
- API. Fidelity with the EC2 API and the installation experience for this functionality are
- both enhanced. In prior releases, users were required to install a separate component
- called CloudBridge, in addition to installing the Management Server. For new installations
- of CloudStack 4.0.0-incubating, this software is installed automatically along with
- CloudStack and runs in a more closely integrated fashion. The feature is disabled by
- default, but can be easily enabled by setting the appropriate global configuration
- parameter and performing a few setup steps.</para>
- </section>
- <section id="nicira-nvp-plugin">
- <title>The Nicira NVP Plugin</title>
- <para>The Nicira NVP plug-in allows CloudStack to use the Nicira solution for virtualized
- network as a provider for CloudStack networks and services. In CloudStack 4.0.0-incubating
- this plug-in supports the Connectivity service. This service is responsible for creating
- Layer 2 networks supporting the networks created by guests. When a tenant creates a new
- network, instead of a traditional VLAN, a logical network will be created by sending the
- appropriate calls to the Nicira NVP Controller. The plug-in has been tested with Nicira
- NVP versions 2.1.0, 2.2.0 and 2.2.1.</para>
- </section>
- <section id="castor-support">
- <title>Support for CAStor Cluster</title>
- <para>CloudStack 4.0.0-incubating supports using a CAStor cluster as the back-end storage
- system for a CloudStack S3 front-end. The CAStor back-end storage for CloudStack extends
- the existing storage classes and allows the storage configuration attribute to point to a
- CAStor cluster. This feature makes use of the CloudStack server's local disk to spool
- files before writing them to CAStor when handling the PUT operations. However, a file must
- be successfully written into the CAStor cluster prior to the return of a success code to
- the S3 client to ensure that the transaction outcome is correctly reported.</para>
- <para>The S3 multipart file upload is not supported in this release. You are prompted with
- proper error message if a multipart upload is attempted.</para>
- </section>
- <section id="clvm-support-kvm">
- <title>Clustered Logical Volume Manager Support for KVM</title>
- <para>This release adds Clustered Logical Volume Manager (CLVM) storage support for KVM
- hosts. With this support, you can use CLVM as primary storage.</para>
- <para>The CLVM support for KVM allows root and data disks (primary storage) to reside on
- Linux logical volumes. The administrators are required to configure CLVM on the KVM hosts
- independent of CloudStack. When the volume groups are available, an administrator can
- simply add primary storage of type CLVM, providing the volume group name. Then CloudStack
- creates and manages logical volumes as needed.</para>
- <para>CLVM also supports Snapshots. CloudStack creates an LVM snapshot, copy the applicable
- logical volume to the secondary storage in the qcow2 format, and then delete the LVM
- snapshot. </para>
- </section>
- <section id="rbd-support-kvm">
- <title>Rados Block Device Support for KVM</title>
- <para>You can now use Rados Block Device (RBD) to run instances on Apache CloudStack
- 4.0.0-incubating. This can be done by adding a RBD pool as primary storage. Before using
- RBD, ensure that Qemu is compiled with RBD enabled, and the libvirt version is at least
- 0.10 with RBD enabled on the KVM host </para>
- <para>Create a disk offering for RBD so that you can ensure that StoragePoolAllocator
- chooses the RBD pool to deploy instances.</para>
- </section>
+ <title>What’s New in 4.0.1-incubating</title>
+ <para>Apache CloudStack 4.0.1-incubating is a bugfix release and includes no new features.</para>
</section>
<section id="issues-fixed-4.0">
- <title>Issues Fixed in 4.0.0-incubating</title>
- <para>Many bugs include a defect number that reflects the bug number that was held in the bug
- tracker run by Citrix (bugs.cloudstack.org). The Apache CloudStack project now uses <ulink
- url="https://issues.apache.org/jira/browse/CLOUDSTACK">Jira</ulink> to manage its bugs, so
- some of the bugs that are referenced here may not be available to view. However, we are
- still including them for completeness.</para>
+ <title>Issues Fixed in 4.0.1-incubating</title>
+ <para>The following issues have been fixed in 4.0.1-incubating:</para>
<informaltable>
<tgroup cols="2" align="left" colsep="1" rowsep="1">
<colspec colwidth="1*" colname="1" colnum="1"/>
@@ -1347,1075 +1116,136 @@ Done restarting router(s).
</thead>
<tbody>
<row>
- <entry><para>Many</para></entry>
- <entry><para>vSphere 5.0 now has GA support. Formerly only Beta support was
- provided.</para></entry>
- </row>
- <row>
- <entry><para>CS-16135</para></entry>
- <entry><para>Creating volumes after upgrading from snapshot taken in 2.2.14 no longer
- deletes the snapshot physically from the secondary storage.</para></entry>
- </row>
- <row>
- <entry><para>CS-16122</para></entry>
- <entry><para>In a site-to-site VPN setup, alerts are generated when the VPC virtual
- router is rebooted with multiple vpn connections.</para></entry>
- </row>
- <row>
- <entry><para>CS-16022</para></entry>
- <entry><para>If host connection fails due to a database error, host now disconnects
- and the Managerment Server id is removed.</para></entry>
- </row>
- <row>
- <entry><para>CS-16011</para></entry>
- <entry><para>Name of network offering is no longer truncated due to too-narrow field
- width in Add Guest Network dialog box. </para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15978</para></entry>
- <entry><para>When the virtual router and its host go down, the high availability
- mechanism now works for the virtual router.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15921</para></entry>
- <entry><para>The 2.2.x security group script now accounts for the VMs created in the
- version 2.1 timeframe.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15919</para></entry>
- <entry><para>A level parameter is added to the listVolumes command; therefore queries
- return the response more quickly.</para></entry>
- </row>
- <row>
- <entry><para>CS-15904</para></entry>
- <entry><para>Upgrade from version 2.2.14 to CloudStack-3.0.5-0.2944-rhel5 works as
- expected. The upgrade script,
- /usr/share/cloud/setup/db/schema-2214to30-cleanup.sql, works as
- expected.</para></entry>
- </row>
- <row>
- <entry><para>CS-15879</para></entry>
- <entry><para>The database upgrade from version 3.0.4 to 3.0.5 works as
- expected.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15807</para></entry>
- <entry><para>Network label for OVM now available in UI.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15779</para></entry>
- <entry><para>When the thumbnail is requested, the console session will not be
- terminated.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15778</para></entry>
- <entry><para>Fetching a VM thumbnail now gets a thumbnail of appropriate visual
- dimensions.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15734</para></entry>
- <entry><para>KVM Snapshots no longer shows incorrect disk usage.</para></entry>
- </row>
- <row>
- <entry><para>CS-15733</para></entry>
- <entry><para>The domainId parameter for the listNetworks command now lists the
- resources belonging to the domain specified.</para></entry>
- </row>
- <row>
- <entry><para>CS-15676</para></entry>
- <entry><para>Stopping the router no longer fails with the null pointer
- exception.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15648</para></entry>
- <entry><para>If creating a volume from a snapshot fails, the error is reported on the
- UI but the volume is stuck in the creating state.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15646</para></entry>
- <entry><para>createFirewallRule API no longer causes null pointer
- exception.</para></entry>
- </row>
- <row>
- <entry><para>CS-15628</para></entry>
- <entry><para>In a KVM host, the high availability mechanism no longer takes a long
- time to migrate VMs to another KVM host if there are multiple storage
- pools.</para></entry>
- </row>
- <row>
- <entry><para>CS-15627</para></entry>
- <entry><para>Metadata instance-id and vm-id for existing VMs stays the same after
- upgrade.</para></entry>
- </row>
- <row>
- <entry><para>CS-15621</para></entry>
- <entry><para>Solved difficulty with allocating disk volumes when running multiple VM
- deployment in parallel.</para></entry>
- </row>
- <row>
- <entry><para>CS-15603</para></entry>
- <entry><para>CloudStack now stop the VMs when destroyVM command is
- called.</para></entry>
- </row>
- <row>
- <entry><para>CS-15586</para></entry>
- <entry><para>Public Vlan for an account no longer fails if multiple physical networks
- are present.</para></entry>
- </row>
- <row>
- <entry><para>CS-15582</para></entry>
- <entry><para>The dns-name filter is now supported for ec2-describe-instances in the
- Amazon Web Services API compatibility commands. The filter maps to the name of a
- user VM.</para></entry>
- </row>
- <row>
- <entry><para>CS-15503</para></entry>
- <entry><para>An IP address which has static NAT rules can now be released.
- Subsequently, restarting this network after it was shutdown can
- succeed.</para></entry>
- </row>
- <row>
- <entry><para>CS-15464</para></entry>
- <entry><para>Can now delete static route whose state is set to Revoke.</para></entry>
- </row>
- <row>
- <entry><para>CS-15443</para></entry>
- <entry><para>Creating a firewall rule no longer fails with an internal server
- error.</para></entry>
- </row>
- <row>
- <entry><para>CS-15398</para></entry>
- <entry><para>Corrected technique for programming DNS on the user VMs.</para></entry>
- </row>
- <row>
- <entry><para>CS-15356</para></entry>
- <entry><para>Internal DNS 2 entry now correctly shown in UI.</para></entry>
- </row>
- <row>
- <entry><para>CS-15335</para></entry>
- <entry><para>The CloudBridge S3 Engine now connects to the database by using the
- deciphered password in the db.properties file.</para></entry>
- </row>
- <row>
- <entry><para>CS-15318</para></entry>
- <entry><para>UI now correctly prevents the user from stopping a VM that is in the
- Starting state.</para></entry>
- </row>
- <row>
- <entry><para>CS-15307</para></entry>
- <entry><para>Fixed Japanese localization of instance statuses in the Instances
- menu.</para></entry>
- </row>
- <row>
- <entry><para>CS-15278</para></entry>
- <entry><para>The deployment planner no longer takes long time to locate a suitable
- host to deploy VMs when large number of clusters are present.</para></entry>
- </row>
- <row>
- <entry><para>CS-15274</para></entry>
- <entry><para>Creating a VLAN range using Zone ID without network ID now
- succeeds.</para></entry>
- </row>
- <row>
- <entry><para>CS-15243</para></entry>
- <entry><para>Now check to be sure source NAT and VPN have same
- provider.</para></entry>
- </row>
- <row>
- <entry><para>CS-15232</para></entry>
- <entry><para>Ensure that networks using external load balancer/firewall in 2.2.14 or
- earlier can properly upgrade.</para></entry>
- </row>
- <row>
- <entry><para>CS-15200</para></entry>
- <entry><para>No exception when trying to attach the same volume while attaching the
- first volume is in progress.</para></entry>
- </row>
- <row>
- <entry><para>CS-15173</para></entry>
- <entry><para>Additional cluster can no longer be added with same VSM IP address as
- another cluster.</para></entry>
- </row>
- <row>
- <entry><para>CS-15167</para></entry>
- <entry><para>AWS API calls now honor the admin account's ability to view or act on the
- resources owned by the regular users.</para></entry>
- </row>
- <row>
- <entry><para>CS-15163</para></entry>
- <entry><para>The minimum limit is not honored when there is not enough capacity to
- deploy all the VMs and the ec2-run-instances command with the -n >n1 -n2>
- option is used to deploy multiple VMs.</para></entry>
- </row>
- <row>
- <entry><para>CS-15157</para></entry>
- <entry><para>Can now add/enable service providers for multiple physical networks
- through the UI.</para></entry>
- </row>
- <row>
- <entry><para>CS-15145</para></entry>
- <entry><para>AWS API call ec2-register has better error handling for negative
- cases.</para></entry>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-359">CLOUDSTACK-359</ulink></para></entry>
+ <entry><para>PropagateResourceEventCommand failes in cluster configuration.</para></entry>
</row>
- <row>
- <entry><para>CS-15122</para></entry>
- <entry><para>Filters now supported for AWS API call
- ec2-describe-availability-zones.</para></entry>
- </row>
- <row>
- <entry><para>CS-15120</para></entry>
- <entry><para>Actions column in UI of Volume page now shows action
- links.</para></entry>
- </row>
- <row>
- <entry><para>CS-15099</para></entry>
- <entry><para>Buttons no longer overlap text on Account Deletion confirmation page in
- UI.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-374">CLOUDSTACK-374</ulink></para></entry>
+ <entry><para>When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0).</para></entry>
</row>
- <row>
- <entry><para>CS-15095</para></entry>
- <entry><para>Ensures you can not create a VM with a CPU frequency greater than the
- host CPU frequency.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-389">CLOUDSTACK-389</ulink></para></entry>
+ <entry><para>Install Guide: Section 4.5.5 (Prepare NFS Shares): Confusing statement about iSCSI</para></entry>
</row>
- <row>
- <entry><para>CS-15094</para></entry>
- <entry><para>CPU cap now set properly in VMware.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-395">CLOUDSTACK-395</ulink></para></entry>
+ <entry><para>Primary Storage and Secondary Storage sections missing sub-sections</para></entry>
</row>
- <row>
- <entry><para>CS-15077</para></entry>
- <entry><para>NullPointerException is no longer observed while executing the command to
- list the public IP in a basic zone created with the default shared NetScaler EIP
- and ELB network offering.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-415">CLOUDSTACK-415</ulink></para></entry>
+ <entry><para>restartNetwork call causes VM to be unreachable when Nicira based SDN is used.</para></entry>
</row>
- <row>
- <entry><para>CS-15044</para></entry>
- <entry><para>UI now provides option to view the list of instances which are part of
- the guest network.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-422">CLOUDSTACK-422</ulink></para></entry>
+ <entry><para>XSL files missing license header.</para></entry>
</row>
- <row>
- <entry><para>CS-15026</para></entry>
- <entry><para>UI in Deploy VM dialog now lists only templates or ISOs depending on
- which is selected in previous dialog.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-426">CLOUDSTACK-426</ulink></para></entry>
+ <entry><para>SetVPCStaticNatRules unimplemented for KVM.</para></entry>
</row>
- <row>
- <entry><para>CS-14989</para></entry>
- <entry><para>In KVM, the Create Instance wizard now shows only templates from the
- current (KVM) zone.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-448">CLOUDSTACK-448</ulink></para></entry>
+ <entry><para>SSVM bootstrap failure on XenServer hosts with E3 CPU.</para></entry>
</row>
- <row>
- <entry><para>CS-14986, CS-14985</para></entry>
- <entry><para>Listing filters works as expected in the ec2-describe-volumes and
- ec2-describe-snapshots commands.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-465">CLOUDSTACK-465</ulink></para></entry>
+ <entry><para>French language file quotes are dropping javascript syntax errors.</para></entry>
</row>
- <row>
- <entry><para>CS-14964</para></entry>
- <entry><para>Automatically starting the Console Proxy no longer fails due to its
- missing volume on the primary storage</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-473">CLOUDSTACK-473</ulink></para></entry>
+ <entry><para>API Doc for uploadCustomCertificate doesn't explain how to use the optional parameters well.</para></entry>
</row>
- <row>
- <entry><para>CS-14907</para></entry>
- <entry><para>User is now correctly prevented from trying to download an uploaded
- volume which has not yet been moved to primary storage.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-480">CLOUDSTACK-480</ulink></para></entry>
+ <entry><para>Installation Documentation error: Section 4.5.5.2 needs to mention nfs-kernel-server.</para></entry>
</row>
- <row>
- <entry><para>CS-14879</para></entry>
- <entry><para>When a user VM is stopped or terminated, the static NAT associated with
- this VM is now disabled. This public IP address is no longer owned by this account
- and can be associated to any other user VM.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-498">CLOUDSTACK-498</ulink></para></entry>
+ <entry><para>Missing dependency in RPM of KVM Agent.</para></entry>
</row>
- <row>
- <entry><para>CS-14854</para></entry>
- <entry><para>Only the admin user can change the template permission to Public, so this
- option is removed from the UI for domain Admins and regular Users.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-502">CLOUDSTACK-502</ulink></para></entry>
+ <entry><para>VPC router needs to resolve its hostname.</para></entry>
</row>
- <row>
- <entry><para>CS-14817</para></entry>
- <entry><para>While checking if network has any external provider, CloudStack will
- consider all providers in the network.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-505">CLOUDSTACK-505</ulink></para></entry>
+ <entry><para>CloudStack logs the private key in plaintext.</para></entry>
</row>
- <row>
- <entry><para>CS-14796</para></entry>
- <entry><para>When deploying a VM with ec2-run-instances, userdata is now
- encoded.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-507">CLOUDSTACK-507</ulink></para></entry>
+ <entry><para>fix api docs for listSSHKeyPairs.</para></entry>
</row>
- <row>
- <entry><para>CS-14770</para></entry>
- <entry><para>The API returns the keypair information when a VM is deployed with
- sshkey. This affects the API commands related to virtual machines
- (deployVirtualMachine, listVirtualMachines, ... *VirtualMachine), as well as the
- corresponding AWS APIs.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-515">CLOUDSTACK-515</ulink></para></entry>
+ <entry><para>NVP Installation.</para></entry>
</row>
- <row>
- <entry><para>CS-14724</para></entry>
- <entry><para>UI no longer displays the dropdown list of isolation method choices if
- sdn.ovs.controller is false.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-536">CLOUDSTACK-536</ulink></para></entry>
+ <entry><para>remove citrix cloudpatform from 4.0 build - CloudStack is ASF project.</para></entry>
</row>
- <row>
- <entry><para>CS-14345</para></entry>
- <entry><para>Logout API returns XML header.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-560">CLOUDSTACK-560</ulink></para></entry>
+ <entry><para>Usage server doesn't work in 4.0.0 due to missing db changes.</para></entry>
</row>
- <row>
- <entry><para>CS-14724</para></entry>
- <entry><para>Host IPs now associated with appropriate IPs according to traffic
- type.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-591">CLOUDSTACK-591</ulink></para></entry>
+ <entry><para>Wrong vnet in iptables on KVM hypervisors after VM reboot.</para></entry>
</row>
- <row>
- <entry><para>CS-14253</para></entry>
- <entry><para>Can now delete and re-create port forwarding rule on same
- firewall.</para></entry>
+ <row>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-622">CLOUDSTACK-622</ulink></para></entry>
+ <entry><para>In the add primary storage dialog in the ui the RBD fields don't disappear when changing from RBD to another protocol.</para></entry>
</row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </section>
+ <section id="known-issues-4.0">
+ <title>Known Issues in 4.0.1-incubating</title>
+ <informaltable>
+ <tgroup cols="2" align="left" colsep="1" rowsep="1">
+ <colspec colwidth="1*" colname="1" colnum="1"/>
+ <colspec colwidth="2*" colname="2" colnum="2"/>
+ <thead>
<row>
- <entry><para>CS-14724</para></entry>
- <entry><para>UI no longer displays the dropdown list of isolation method choices if
- sdn.ovs.controller is false.</para></entry>
+ <entry>
+ <para>Issue ID</para>
+ </entry>
+ <entry>
+ <para>Description</para>
+ </entry>
</row>
+ </thead>
+ <tbody>
<row>
- <entry><para>CS-14452</para></entry>
- <entry><para>Data disk volumes are now automatically copied from one cluster to
- another.</para></entry>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-301">CLOUDSTACK-301</ulink></para></entry>
+ <entry><para>Nexus 1000v DVS integration is not functional</para>
+ <para>This source code release includes some partial functionality to support the
+ Cisco Nexus 1000v Distributed Virtual Switch within a VMware hypervisor
+ environment. The functionality is not complete at this time.</para>
+ </entry>
</row>
<row>
- <entry><para>CS-13539</para></entry>
- <entry><para>Windows VM can get IP after reboot.</para></entry>
+ <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-368">CLOUDSTACK-368</ulink></para></entry>
+ <entry><para>OVM - cannot create guest VM</para>
+ <para>This source code release has regressed from the CloudStack 2.2.x code
+ and is unable to support Oracle VM (OVM).</para>
+ </entry>
</row>
<row>
- <entry><para>CS-13537</para></entry>
- <entry><para>When user tries to delete a domain that contains sub-domains, an error
- message is now sent to convey the reason for the delete failure.</para></entry>
- </row>
- <row>
- <entry><para>CS-13153</para></entry>
- <entry><para>System VMs support HTTP proxy.</para></entry>
- </row>
- <row>
- <entry><para>CS-12642</para></entry>
- <entry><para>Added Close button to Select Project list view popup in
- UI.</para></entry>
- </row>
- <row>
- <entry><para>CS-12510</para></entry>
- <entry><para>Deleting and reinserting host_details no longer causes
- deadlocks.</para></entry>
- </row>
- <row>
- <entry><para>CS-12407</para></entry>
- <entry><para>F5 and Netscaler - when dedicated is selected, capacity field is
- disabled.</para></entry>
- </row>
- <row>
- <entry><para>CS-12111</para></entry>
- <entry><para>Email validation for edit user form.</para></entry>
- </row>
- <row>
- <entry><para>CS-10928</para></entry>
- <entry><para>Network read/write values now always positive numbers.</para></entry>
- </row>
- <row>
- <entry><para>CS-15376, CS-15373</para></entry>
- <entry><para>The AWS APIs (EC2 and S3) now listen on the 7080 port and send request to
- CloudStack on the 8080 port just as any other clients of
- CloudStack.</para></entry>
- </row>
- <row>
- <entry><para>CS-13944</para></entry>
- <entry><para>The CloudStack 2.2.x to 3.0.x database upgrade for multiple physical
- networks is now supported.</para></entry>
- </row>
- <row>
- <entry><para>CS-15300</para></entry>
- <entry><para>The admin accounts of a domain now honour the limits imposed on that
- domain just like the regular accounts do. A domain admin now is not allowed to
- create an unlimited number of instances, volumes, snapshots, and so
- on.</para></entry>
- </row>
- <row>
- <entry><para>CS-15396</para></entry>
- <entry><para>The CloudStack database now contain the UUD information after the 2.2.14
- to 3.0.4 upgrade.</para></entry>
- </row>
- <row>
- <entry><para>CS-15450</para></entry>
- <entry><para>Upgrade from 2.2.14 to 3.0.4 no longer fails on a VMware
- host.</para></entry>
- </row>
- <row>
- <entry><para>CS-15449</para></entry>
- <entry><para>Running cloudstack-aws-api-register no longer fails with the "User
- registration failed with error: [Errno 113] No route to host"
- error.</para></entry>
- </row>
- <row>
- <entry><para>CS-15455</para></entry>
- <entry><para>The iptable rules are configured to open the awsapi port (7080) as part
- of the installation.</para></entry>
- </row>
- <row>
- <entry><para>CS-15429</para></entry>
- <entry><para>While creating an instance with data volume, disk offering also is
- considered while checking the account limit on volume resources.</para></entry>
- </row>
- <row>
- <entry><para>CS-15414</para></entry>
- <entry><para>After the 2.2.14 to 3.0.4 upgrade, the value of the global parameter
- xen.guest.network.device is now decrypted before setting the traffic
- label.</para></entry>
- </row>
- <row>
- <entry><para>CS-15382</para></entry>
- <entry><para>During 2.2.14 to 3.0.4 upgrade, the hosts no longer go to the Alert state
- if destroyed networks existed with non-existent tags prior to
- upgrade.</para></entry>
- </row>
- <row>
- <entry><para>CS-15323</para></entry>
- <entry><para>CloudStack supports the following Citrix XenServer hotfixes: XS602E003,
- XS602E004, and XS602E005.</para></entry>
- </row>
- <row>
- <entry><para>CS-15430</para></entry>
- <entry><para>Create snapshot now fails if creating a snapshot exceeds the snapshot
- resource limit for a domain admin or a user account.</para></entry>
- </row>
- <row>
- <entry><para>CS-14256</para></entry>
- <entry><para>Virtual Router no longer remains in starting state for subdomain or user
- on a KVM 3.0.1 prerlease host on RHEL 6.2.</para></entry>
- </row>
- <row>
- <entry><para>CS-7495</para></entry>
- <entry><para>Implemented a variety of Xen management host improvements.</para></entry>
- </row>
- <row>
- <entry><para>CS-8105</para></entry>
- <entry><para>NFS v4 for primary storage now works as expected on KVM
- hosts.</para></entry>
- </row>
- <row>
- <entry><para>CS-9989</para></entry>
- <entry><para>The error messages returned during VM deployment failure will have much
- more details than before.</para></entry>
- </row>
- <row>
- <entry><para>CS-12584</para></entry>
- <entry><para>You can no longer add security groups not supported by the hypervisor in
- use.</para></entry>
- </row>
- <row>
- <entry><para>CS-12705</para></entry>
- <entry><para>When creating a Network offering by using SRX as the service provider for
- SourceNAT servcies, an option is given in the CloudStack UI now to set the
- source_nat type to "per Zone"/"per account". </para></entry>
- </row>
- <row>
- <entry><para>CS-12782</para></entry>
- <entry><para>Assigning a VM from Basic to Advanced zone no longer ignores the network
- ID. A warning message is displayed for VM movements across zones.</para></entry>
- </row>
- <row>
- <entry><para>CS-12591</para></entry>
- <entry><para>Broadcast Address on the Second Public IP NIC is now
- corrected.</para></entry>
- </row>
- <row>
- <entry><para>CS-13272</para></entry>
- <entry><para>When a user is deleted, all the associated properties, such as IPs and
- virtual routers, are now deleted.</para></entry>
- </row>
- <row>
- <entry><para>CS-13377</para></entry>
- <entry><para>Creating template from a root disk of a stopped instance now provides an
- option to make it a "Featured template".</para></entry>
- </row>
- <row>
- <entry><para>CS-13500</para></entry>
- <entry><para>Reaching the first guest VM by using its public IP from the second guest
- VM no longer fails.</para></entry>
- </row>
- <row>
- <entry><para>CS-13853</para></entry>
- <entry><para>The default gateway can no longer be 0.0.0.0 in the Secondary Storage VM
- (SSVM).</para></entry>
- </row>
- <row>
- <entry><para>CS-13863</para></entry>
- <entry><para>The queryAsyncJobResult command in XML format now returns the correct
- UUIDs.</para></entry>
- </row>
- <row>
- <entry><para>CS-13867</para></entry>
- <entry><para>Corrected CSP xenserver-cloud-supp.tgz for XenServer 5.6 and
- 6.0.</para></entry>
- </row>
- <row>
- <entry><para>CS-13904</para></entry>
- <entry><para>Labels and values for the service offerings CPU and memory are now
- consistent. </para></entry>
- </row>
- <row>
- <entry><para>CS-13998</para></entry>
- <entry><para>The SSVM kernel panic issue is fixed on XenServer.</para></entry>
- </row>
- <row>
- <entry><para>CS-14090</para></entry>
- <entry><para>The issue is fixed where running the VMware snapshots randomly fails with
- the ArrayIndexOutOfBoundsException error.</para></entry>
- </row>
- <row>
- <entry><para>CS-14021</para></entry>
- <entry><para>The java.lang.OutOfMemoryError is fixed on the Management
- Server.</para></entry>
- </row>
- <row>
- <entry><para>CS-14025</para></entry>
- <entry><para>The Python Eggs are provided to easily package the test client for each
- branch of CloudStack.</para></entry>
- </row>
- <row>
- <entry><para>CS-14068</para></entry>
- <entry><para>Resetting the VM password through the CloudStack UI no longer causes any
- error.</para></entry>
- </row>
- <row>
- <entry><para>CS-14156</para></entry>
- <entry><para>The pod which has the administrator's virtual router is no longer
- selected while creating the virtual routers for guests.</para></entry>
- </row>
- <row>
- <entry><para>CS-14182</para></entry>
- <entry><para>The users can now delete their ISOs as normal users.</para></entry>
- </row>
- <row>
- <entry><para>CS-14185</para></entry>
- <entry><para>The listOSTypes API now filters out the types of operating system by
- using the keywords.</para></entry>
- </row>
- <row>
- <entry><para>CS-14204</para></entry>
- <entry><para>The cloud-setup-bonding.sh command no longer generates the "command not
- found" error.</para></entry>
- </row>
- <row>
- <entry><para>CS-14214</para></entry>
- <entry><para>The Specify VLAN option cannot be enabled now for an isolated Network
- offering with SourceNAT enabled.</para></entry>
- </row>
- <row>
- <entry><para>CS-14234</para></entry>
- <entry><para>Sending project invite email to an account now requires SMTP configured
- in CloudStack.</para></entry>
- </row>
- <row>
- <entry><para>CS-14237</para></entry>
- <entry><para>The garbage collector of the primary storage no longer fails when the
- first host in the cluster is not up.</para></entry>
- </row>
- <row>
- <entry><para>CS-14241</para></entry>
- <entry><para>Custom Volume Disk Offering is now matching the Global configuration
- value.</para></entry>
- </row>
- <row>
- <entry><para>CS-14270</para></entry>
- <entry><para>The listNetworks API no longer assumes that the broadcast type is always
- VLAN.</para></entry>
- </row>
- <row>
- <entry><para>CS-14319</para></entry>
- <entry><para>The internal name of the VM is no longer present in the error message
- that is displayed to a domain administrator.</para></entry>
- </row>
- <row>
- <entry><para>CS-14321</para></entry>
- <entry><para>The listVolumes API call now returns a valid value for the isExtractable
- parameter for the ISO-derived disk and data disk volumes.</para></entry>
- </row>
- <row>
- <entry><para>CS-14323</para></entry>
- <entry><para>Invalid API calls will now give valid response in json/xml
- format.</para></entry>
- </row>
- <row>
- <entry><para>CS-14339</para></entry>
- <entry><para>Custom Disk Size will now allow values larger than 100GB.</para></entry>
- </row>
- <row>
- <entry><para>CS-14357</para></entry>
- <entry><para>The ConsoleProxyLoadReportCommand is no longer fired
- continuously.</para></entry>
- </row>
- <row>
- <entry><para>CS-14421</para></entry>
- <entry><para>Fixed the issue of virtual router deployments. The DHCP entries can now
- be assigned to the router.</para></entry>
- </row>
- <row>
- <entry><para>CS-14555</para></entry>
- <entry><para>Unzipped downloaded template MD5SUM will no longer override the zipped
- template MD5SUM in the database.</para></entry>
- </row>
- <row>
- <entry><para>CS-14598</para></entry>
- <entry><para>The complete screen of the running VM is now displayed in the console
- proxy.</para></entry>
- </row>
- <row>
- <entry><para>CS-14600</para></entry>
- <entry><para>Windows or Linux based consoles are no longer lost upon rebooting
- VMs.</para></entry>
- </row>
- <row>
- <entry><para>CS-14784</para></entry>
- <entry><para>Multiple subnets with the same VLAN now work as expected.</para></entry>
- </row>
- <row>
- <entry><para>CS-13303, 14874, 13897, 13944, 14088, 14190</para></entry>
- <entry><para>A variety of upgrade issues have been fixed in release
- 3.0.3.</para></entry>
- </row>
- <row>
- <entry><para>CS-15080</para></entry>
- <entry><para>Setting a private network on a VLAN for VMWare environment is now
- supported.</para></entry>
- </row>
- <row>
- <entry><para>CS-15168</para></entry>
- <entry><para>The console proxy now works as expected and no exception is shown in the
- log after upgrading from version 2.2.14 to 3.0.2.</para></entry>
- </row>
- <row>
- <entry><para>CS-15172</para></entry>
- <entry><para>Version 3.0.2 now accepts the valid public key.</para></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- </section>
- <section id="known-issues-4.0">
- <title>Known Issues in 4.0.0-incubating</title>
- <informaltable>
- <tgroup cols="2" align="left" colsep="1" rowsep="1">
- <colspec colwidth="1*" colname="1" colnum="1"/>
- <colspec colwidth="2*" colname="2" colnum="2"/>
- <thead>
- <row>
- <entry>
- <para>Issue ID</para>
- </entry>
- <entry>
- <para>Description</para>
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><para>CLOUDSTACK-301</para></entry>
- <entry><para>Nexus 1000v DVS integration is not functional</para>
- <para>This source code release includes some partial functionality to support the
- Cisco Nexus 1000v Distributed Virtual Switch within a VMware hypervisor
- environment. The functionality is not complete at this time.</para>
- </entry>
- </row>
- <row>
- <entry><para>CLOUDSTACK-368</para></entry>
- <entry><para>OVM - cannot create guest VM</para>
- <para>This source code release has regressed from the CloudStack 2.2.x code
- and is unable to support Oracle VM (OVM).</para>
- </entry>
- </row>
- <row>
- <entry><para>CLOUDSTACK-279</para></entry>
- <entry><para>Deleting a project fails when executed by the regular user. This works as
- expected for root/domain admin. To workaround, perform either of the
- following:</para><itemizedlist>
- <listitem>
- <para>Use the account cleanup thread which will eventually complete the project
- deletion.</para>
- </listitem>
- <listitem>
- <para>Execute the call as the root/domain admin on behalf of the regular
- user.</para>
- </listitem>
- </itemizedlist>
- </entry>
- </row>
- <row>
- <entry><para>CS-16067</para></entry>
- <entry><para>The command=listTags&key=city command does not work as expected. The
- command does not return tags for the resources of the account with the tag, city
- </para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16063</para></entry>
- <entry><para>The current values of volumes and snapshots are incorrect when using KVM
- as a host. To fix this, the database upgrade codes, volumes.size and
- snapshots.size, should be changed to show the virtual sizes.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16058</para></entry>
- <entry><para>Null pointer Exception while deleting the host after moving the host to
- maintenance state.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16045</para></entry>
- <entry><para>Only the root administrator can handle the API keys. The domain
- administrators are not allowed to create, delete, or retrieve API keys for the
- users in their domain. </para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16019</para></entry>
- <entry><para>CIDR list in the Add VPN Customer Gateway dialog does not prompt the user
- that they can provide a comma separated CIDRs if multiple CIDRs have to be
- supplied.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16015</para></entry>
- <entry><para>Deleting a network is not supported when its network providers are
- disabled.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16012</para></entry>
- <entry><para>Unable to delete a zone in the UI because the necessary cleanup cannot be
- completed. When the hosts are removed, the expunge process fails to delete the
- volumes as no hosts are present to send the commands to. Therefore, the storage
- pool removal fails, and zone can't be cleaned and deleted.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-16011</para></entry>
- <entry><para>Name of network offering might be truncated due to too-narrow field width
- in Add Guest Network dialog box.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15789</para></entry>
- <entry><para>Invalid global setting prevents management server to restart. For
- example, if you configure the "project.invite.timeout" parameter to "300" and
- attempt to restart management server, it fails without throwing a warning or
- setting the value to the default.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15749</para></entry>
- <entry><para>Restarting VPC is resulting in intermittent connection loss to the port
- forwarding and StaticNAT rules.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15690</para></entry>
- <entry><para>The IpAssoc command failed as a part of starting the virtual router, but
- the final start result is reported as succes.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15672, CS-15635</para></entry>
- <entry><para>The FQDN of the VM is not configured if it is deployed as a part of
- default shared network and isolated guest network
- (DefaultIsolatedNetworkOfferingWithSourceNatService).</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15634</para></entry>
- <entry><para>The FQDN of a VM that is deployed as a part of both a shared network and
- default isolated guest network has the suffix of the shared network instead of the
- default isolated guest network.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15576</para></entry>
- <entry><para>Stopping a VM on XenServer creates a backlog of API commands. For
- example, the Attach volume calls become delayed while waiting for the
- stopVirtualMachine command to be executed.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15569</para></entry>
- <entry><para>Misleading error message in the exception when creating a StaticNAT rule
- fails in a VPC.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15566</para></entry>
- <entry><para>External device such as Netscaler is not supported in VPC.</para></entry>
- </row>
- <row>
- <entry><para>CS-15557</para></entry>
- <entry><para>Intermittent traffic loss in the VPN connection if Juniper is the remote
- router and the life time is 300 seconds.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15361</para></entry>
- <entry><para>Egress rules are not working in NetScaler loadbalancer.</para>
- </entry>
- </row>
- <row>
- <entry><para>CS-15163</para></entry>
- <entry><para>The minimum limit is not honored when there is not enough capacity to
- deploy all the VMs and the ec2-run-instances command with the -n >n1 -n2>
- option is used to deploy multiple VMs.</para></entry>
- </row>
- <row>
- <entry><para>CS-15105</para></entry>
- <entry><para>The cloud-sysvmadm script does not work if the integration.api.port
- parameter is set to any port other than 8096.</para></entry>
- </row>
- <row>
- <entry><para>CS-15092</para></entry>
- <entry><para>Connecting to the guest VMs through SSH is extremely slow, and it results
- in connection timeout.</para></entry>
- </row>
- <row>
- <entry><para>CS-15037</para></entry>
- <entry><para>Hairpin NAT is not supported when NetScaler is used for
- EIP.</para></entry>
- </row>
- <row>
- <entry><para>CS-15009</para></entry>
- <entry><para>The port_profile table will not be populated with port profile
- information. In this release, CloudStack directly connects to the VSM for all the
- port profile operations; therefore, no port profile information is
- cached.</para></entry>
- </row>
- <row>
- <entry><para>CS-14939</para></entry>
- <entry><para>Adding a VMware cluster is not supported when the Management Network is
- migrated to the Distributed Virtual Switch environment.</para></entry>
- </row>
- <row>
- <entry><para>CS-14780</para></entry>
- <entry><para>You are allowed to ping the elastic IP address of the VM even though no
- ingress rule is set that allows the ICMP protocol.</para></entry>
- </row>
- <row>
- <entry><para>CS-14756</para></entry>
- <entry><para>Installing KVM on RHEL 6.2 will result in unreliable network performance.
- Workaround: blacklist vhost-net. Edit /etc/modprobe.d/blacklist-kvm.conf and
- include vhost-net.</para></entry>
- </row>
- <row>
- <entry><para>CS-14346</para></entry>
- <entry><para>The UpdateVirtualMachine API call does not check whether the VM is
- stopped. Therefore, stop the VM manually before issuing this call.</para></entry>
- </row>
- <row>
- <entry><para>CS-14303 (was 14537)</para></entry>
- <entry><para>The IP addresses for a shared network are still being consumed even if no
- services are defined for that network.</para></entry>
- </row>
- <row>
- <entry><para>CS-14296 (was 14530)</para></entry>
- <entry><para>OVM: Network traffic labels are not supported.</para></entry>
- </row>
- <row>
- <entry><para>CS-14291 (was 14523)</para></entry>
- <entry><para>The EIP/ELB network offering for basic zones does not support multiple
- NetScalers.</para></entry>
- </row>
- <row>
- <entry><para>CS-14275 (was 14506)</para></entry>
- <entry><para>F5: Unable to properly remove a F5 device.</para></entry>
- </row>
- <row>
- <entry><para>CS-14201 (was 14430)</para></entry>
- <entry><para>VMWare: Template sizes are being reported different depending on whether
- the primary storage is using ISCSI or NFS.</para></entry>
- </row>
- <row>
- <entry><para>CS-13758 (was 13963)</para></entry>
- <entry><para>vSphere: template download from templates created off of the root volume
- does not work properly.</para></entry>
- </row>
- <row>
- <entry><para>CS-13733 (was 13935)</para></entry>
- <entry><para>vSphere: detaching an ISO from a restored VM instance
- fails.</para></entry>
- </row>
- <row>
- <entry><para>CS-13682 (was 13883)</para></entry>
- <entry><para>Multiple NetScalers are not supported in Basic Networking.</para></entry>
- </row>
- <row>
- <entry><para>CS-13599 (was 13359)</para></entry>
- <entry><para>Programming F5/NetScaler rules can be better optimized.</para></entry>
- </row>
- <row>
- <entry><para>CS-13337 (was 13518)</para></entry>
- <entry><para>Security Groups are not supported in Advanced Networking</para></entry>
- </row>
- <row>
- <entry><para>CS-13173 (was 13336)</para></entry>
- <entry><para>vSphere: cross cluster volume migration does not work
- properly.</para></entry>
- </row>
- <row>
- <entry><para>CS-12714 (was 12840)</para></entry>
- <entry><para>Capacity view is not available for pods or clusters.</para></entry>
- </row>
- <row>
- <entry><para>CS-12624 (was 12741)</para></entry>
- <entry><para>vSphere: maintenance mode will not live migrate system VM to another
- host.</para></entry>
- </row>
- <row>
- <entry>
- <para>CS-15476</para>
- </entry>
- <entry>
- <para>The 2.2.14 to 4.0.0-incubating upgrade fails if multiple untagged physical
- networks exist before the upgrade.</para>
- </entry>
- </row>
- <row>
- <entry>
- <para>CS-15407</para>
- </entry>
- <entry>
- <para>After the 2.2.14 to 4.0.0-incubating upgrade, VLAN allocation on multiple
- physical networks does not happen as expected.</para>
- <para>To workaround this issue, follow the instructions given below:</para>
- <orderedlist>
- <listitem>
- <para>Revert to your 2.2.14 setup.</para>
- </listitem>
- <listitem>
- <para>Stop all the VMs with the isolated virtual networks in your cloud
- setup.</para>
- </listitem>
- <listitem>
- <para> Run following query to find if any networks still have the NICs
- allocated:</para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>Check if any virtual guest networks have the NICs allocated:</para>
- <programlisting>#SELECT DISTINCT op.id from `cloud`.`op_networks` op JOIN `cloud`.`networks` n on op.id=n.id WHERE nics_count != 0 AND guest_type = 'Virtual'; </programlisti
<TRUNCATED>