CLOUDSTACK-1159 - Remove version number 3.0.3 appears in docs

Signed-off-by: Joe Brockmeier <jzb@zonker.net>
This commit is contained in:
Milamber 2013-03-01 20:06:26 +00:00 committed by Joe Brockmeier
parent 6dfb2f221d
commit d67d435e00
5 changed files with 4 additions and 6 deletions

View File

@ -24,7 +24,7 @@
<section id="added-error-codes">
<title>Added &PRODUCT; Error Codes</title>
<para>You can now find the &PRODUCT;-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode. These codes are applicable in &PRODUCT; 3.0.3 and later versions.</para>
<para>You can now find the &PRODUCT;-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode.</para>
<informaltable frame="all">
<tgroup cols="3" align="left" colsep="1" rowsep="1">
<colspec colname="c1" />

View File

@ -24,7 +24,6 @@
<section id="create-bare-metal-template">
<title>Creating a Bare Metal Template</title>
<note><para><emphasis role="bold">Beta feature. Untested in &PRODUCT; 3.0.3. Provided without guarantee of performance</emphasis>.</para></note>
<para>Before you can create a bare metal template, you must have performed several other installation and setup steps to create a bare metal cluster and environment. See Bare Metal Installation in the Installation Guide. It is assumed you already have a directory named "win7_64bit" on your CIFS server, containing the image for the bare metal instance. This directory and image are set up as part of the Bare Metal Installation procedure.</para>
<orderedlist>
<listitem><para>Log in to the &PRODUCT; UI as an administrator or end user.</para></listitem>

View File

@ -23,7 +23,7 @@
<section id="creating-vms">
<title>Creating VMs</title>
<para>Virtual machines are usually created from a template. Users can also create blank virtual machines. A blank virtual machine is a virtual machine without an OS template. Users can attach an ISO file and install the OS from the CD/DVD-ROM.</para>
<note><para>Starting with v3.0.3, you can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A new request parameter, startVM, is introduced in the deployVm API to support this feature. For more information, see the Developer's Guide</para></note>
<note><para>You can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A request parameter, startVM, in the deployVm API provides this feature. For more information, see the Developer's Guide</para></note>
<para>To create a VM from a template:</para>
<orderedlist>
<listitem><para>Log in to the &PRODUCT; UI as an administrator or user.</para></listitem>

View File

@ -24,7 +24,7 @@
<section id="dedicated-ha-hosts">
<title>Dedicated HA Hosts</title>
<para>(v3.0.3 and greater) One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:</para>
<para>One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:</para>
<itemizedlist>
<listitem><para>Make it easier to determine which VMs have been restarted as part of the &PRODUCT; high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.).</para></listitem>
<listitem><para>Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes.</para></listitem>

View File

@ -25,8 +25,7 @@
<title>Shared Networks</title>
<para>A shared network can be accessed by virtual machines that belong to many different
accounts. Network Isolation on shared networks is accomplished using techniques such as
security groups (supported only in basic zones in &PRODUCT; 3.0.3 and later
versions).</para>
security groups (supported only in basic zones).</para>
<itemizedlist>
<listitem><para>Shared Networks are created by the administrator</para></listitem>
<listitem><para>Shared Networks can be designated to a certain domain</para></listitem>