mirror of https://github.com/apache/cloudstack.git
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/incubator-cloudstack
This commit is contained in:
David Nalley
commit
7bbdad1299
|
|
@ -27,7 +27,7 @@
|
|||
<title>&PRODUCT; Guide</title>
|
||||
<subtitle>Revised August 9, 2012 10:48 pm Pacific</subtitle>
|
||||
<productname>Apache CloudStack</productname>
|
||||
<productnumber>4.0</productnumber>
|
||||
<productnumber>4.0.0-incubating</productnumber>
|
||||
<edition>1</edition>
|
||||
<pubsnumber></pubsnumber>
|
||||
<abstract>
|
||||
|
|
|
|||
|
|
@ -19,13 +19,13 @@
|
|||
under the License.
|
||||
-->
|
||||
<bookinfo id="book-release-notes-4.0">
|
||||
<title>Version 4.0 Release Notes</title>
|
||||
<title>Version 4.0.0-incubating Release Notes</title>
|
||||
<subtitle>Revised October 17, 2012 19:49 UTC</subtitle>
|
||||
<productname>Apache CloudStack</productname>
|
||||
<productnumber/>
|
||||
<pubsnumber/>
|
||||
<abstract>
|
||||
<para>Release notes for the Apache CloudStack 4.0 release.</para>
|
||||
<para>Release notes for the Apache CloudStack 4.0.0-incubating release.</para>
|
||||
</abstract>
|
||||
<corpauthor>
|
||||
<inlinemediaobject>
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
<bookinfo id="cloudstack_plugin_niciranvp">
|
||||
<title>&PRODUCT; Plugin Guide for the Nicira NVP Plugin</title>
|
||||
<productname>Apache CloudStack</productname>
|
||||
<productnumber>4.0</productnumber>
|
||||
<productnumber>4.0.0-incubating</productnumber>
|
||||
<edition>1</edition>
|
||||
<pubsnumber></pubsnumber>
|
||||
<abstract>
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@
|
|||
<title>About Clusters</title>
|
||||
<para>
|
||||
A cluster provides a way to group hosts. To be precise, a cluster is a
|
||||
XenServer server pool, a set of KVM servers, a set of OVM hosts, or a
|
||||
XenServer server pool, a set of KVM servers, <!-- a set of OVM hosts -->, or a
|
||||
VMware cluster preconfigured in vCenter. The hosts in a cluster all
|
||||
have identical hardware, run the same hypervisor, are on the same subnet,
|
||||
and access the same shared primary storage. Virtual machine instances
|
||||
|
|
|
|||
|
|
@ -24,6 +24,6 @@
|
|||
so before you begin adding hosts to the cloud, you must add at least one cluster.</para>
|
||||
<xi:include href="about-clusters.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
<xi:include href="add-clusters-kvm-xenserver.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
<xi:include href="add-clusters-ovm.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
<!-- <xi:include href="add-clusters-ovm.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> -->
|
||||
<xi:include href="add-clusters-vsphere.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
under the License.
|
||||
-->
|
||||
<section id="added-API-commands-4.0">
|
||||
<title>Added API Commands in 4.0</title>
|
||||
<title>Added API Commands in 4.0.0-incubating</title>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>createCounter (Adds metric counter)</para>
|
||||
|
|
@ -161,4 +161,4 @@
|
|||
as the IP address of the Nexus 1000v dvSwitch.)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</section>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -180,9 +180,9 @@
|
|||
<listitem>
|
||||
<para>KVM Installation and Configuration</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<!-- <listitem>
|
||||
<para>Oracle VM (OVM) Installation and Configuration</para>
|
||||
</listitem>
|
||||
</listitem> -->
|
||||
</itemizedlist>
|
||||
<para>To configure the first host, enter the following, then click Next:</para>
|
||||
<itemizedlist>
|
||||
|
|
|
|||
|
|
@ -37,7 +37,8 @@
|
|||
</inlinemediaobject>
|
||||
</para></listitem>
|
||||
<listitem><para>In the Instance popup, choose the VM to which you want to attach the volume. You will only see instances to which you are allowed to attach volumes; for example, a user will see only instances created by that user, but the administrator will have more choices.</para>
|
||||
<para>If the VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para></listitem>
|
||||
<!-- <para>If the VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
|
||||
</listitem>
|
||||
<listitem><para>When the volume has been attached, you should be able to see it by clicking Instances, the instance name, and View Volumes.</para></listitem>
|
||||
</orderedlist>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@
|
|||
<listitem><para>Citrix XenServer Installation and Configuration</para></listitem>
|
||||
<listitem><para>VMware vSphere Installation and Configuration</para></listitem>
|
||||
<listitem><para>KVM vSphere Installation and Configuration</para></listitem>
|
||||
<listitem><para>Oracle VM (OVM) Installation and Configuration</para></listitem>
|
||||
<!-- <listitem><para>Oracle VM (OVM) Installation and Configuration</para></listitem> -->
|
||||
</itemizedlist>
|
||||
<para>To configure the first host, enter the following, then click Next:</para>
|
||||
<itemizedlist>
|
||||
|
|
|
|||
|
|
@ -26,35 +26,98 @@
|
|||
<title>Building DEB packages</title>
|
||||
<para>
|
||||
In addition to the bootstrap dependencies, you'll also need to install
|
||||
a few other dependencies by issuing the following commands:
|
||||
<programlisting><prompt>#</prompt> <command>apt-get</command> update</programlisting>
|
||||
<programlisting><prompt>$</prompt> <command>apt-get</command> install debhelper openjdk-6-jdk tomcat6 libws-commons-util-java genisoimage python-mysqldb</programlisting>
|
||||
</para>
|
||||
several other dependencies. Note that we recommend using Maven 3, which
|
||||
is not currently available in 12.04.1 LTS. So, you'll also need to add a
|
||||
PPA repository that includes Maven 3. After running the command
|
||||
<command>add-apt-repository</command>, you will be prompted to continue and
|
||||
a GPG key will be added.
|
||||
</para>
|
||||
<screen>
|
||||
<command>$ sudo apt-get update</command>
|
||||
<command>$ sudo apt-get install python-software-properties</command>
|
||||
<command>$ sudo add-apt-repository ppa:natecarlson/maven3</command>
|
||||
<command>$ sudo apt-get update</command>
|
||||
<command>$ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6 libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven3</command>
|
||||
</screen>
|
||||
<para>
|
||||
While we have defined, and you have presumably already installed the
|
||||
bootstrap prerequisites, there are a number of build time prerequisites
|
||||
that need to be resolved. &PRODUCT; uses maven for dependency resolution.
|
||||
You can resolve the buildtime depdencies for CloudStack by running the
|
||||
following command:
|
||||
<programlisting><prompt>$</prompt> <command>mvn</command> -P deps</programlisting>
|
||||
</para>
|
||||
You can resolve the buildtime depdencies for CloudStack by running:</para>
|
||||
|
||||
<screen><command>$ mvn3 -P deps</command></screen>
|
||||
<para>
|
||||
Now that we have resolved the dependencies we can move on to building &PRODUCT;
|
||||
and packaging them into DEBs by issuing the following command.
|
||||
<programlisting><prompt>#</prompt> <command>dpkg-buildpackage</command></programlisting>
|
||||
</para>
|
||||
<screen>
|
||||
<command>$ dpkg-buildpackge -uc -us</command>
|
||||
</screen>
|
||||
|
||||
<para>
|
||||
This command will build 16 Debian packages. You should have all of the following:
|
||||
</para>
|
||||
<programlisting>
|
||||
cloud-agent_4.0.0-incubating_amd64.deb
|
||||
cloud-agent-deps_4.0.0-incubating_amd64.deb
|
||||
cloud-agent-libs_4.0.0-incubating_amd64.deb
|
||||
cloud-awsapi_4.0.0-incubating_amd64.deb
|
||||
cloud-cli_4.0.0-incubating_amd64.deb
|
||||
cloud-client_4.0.0-incubating_amd64.deb
|
||||
cloud-client-ui_4.0.0-incubating_amd64.deb
|
||||
cloud-core_4.0.0-incubating_amd64.deb
|
||||
cloud-deps_4.0.0-incubating_amd64.deb
|
||||
cloud-python_4.0.0-incubating_amd64.deb
|
||||
cloud-scripts_4.0.0-incubating_amd64.deb
|
||||
cloud-server_4.0.0-incubating_amd64.deb
|
||||
cloud-setup_4.0.0-incubating_amd64.deb
|
||||
cloud-system-iso_4.0.0-incubating_amd64.deb
|
||||
cloud-usage_4.0.0-incubating_amd64.deb
|
||||
cloud-utils_4.0.0-incubating_amd64.deb
|
||||
</programlisting>
|
||||
|
||||
<section id="sect-source-builddebs-repo">
|
||||
<title>Setting up an APT repo</title>
|
||||
<para>TBD</para>
|
||||
|
||||
<para>After you've created the packages, you'll want to copy them to a system where you can serve the packages over HTTP. You'll create a directory for the packages and then use <code>dpkg-scanpackages</code> to create <filename>Packages.gz</filename>, which holds information about the archive structure. Finally, you'll add the repository to your system(s) so you can install the packages using APT.</para>
|
||||
|
||||
<para>The first step is to make sure that you have the <application>dpkg-dev</application> package installed. This should have been installed when you pulled in the <application>debhelper</application> application previously, but if you're generating <filename>Packages.gz</filename> on a different system, be sure that it's installed there as well.</para>
|
||||
|
||||
<screen><command>$ sudo apt-get install dpkg-dev</command></screen>
|
||||
|
||||
<para>The next step is to copy the DEBs to the directory where they can be served over HTTP. We'll use <filename>/var/www/cloudstack/repo</filename> in the examples, but change the directory to whatever works for you.</para>
|
||||
|
||||
<screen>
|
||||
<command>sudo mkdir -p /var/www/cloudstack/repo/binary</command>
|
||||
<command>sudo cp *.deb /var/www/cloudstack/repo/binary</command>
|
||||
<command>sudo cd /var/www/cloudstack/repo/binary</command>
|
||||
<command>sudo dpkg-scanpackages . /dev/null | tee Packages | gzip -9 > Packages.gz</command>
|
||||
</screen>
|
||||
|
||||
<note><title>Note: Override Files</title>
|
||||
<para>You can safely ignore the warning about a missing override file.</para>
|
||||
</note>
|
||||
|
||||
<para>Now you should have all of the DEB packages and <filename>Packages.gz</filename> in the <filename>binary</filename> directory and available over HTTP. (You may want to use <command>wget</command> or <command>curl</command> to test this before moving on to the next step.)</para>
|
||||
|
||||
</section>
|
||||
<section id="sect-source-builddebs-repo2">
|
||||
<title>Configuring your machines to use the APT repository</title>
|
||||
<para>
|
||||
Now that we have created the repository, you need to configure your machine
|
||||
to make use of the APT repository. We do that by issuing the following commands:
|
||||
<programlisting><prompt>$</prompt> <command>echo</command> "deb <replaceable>http://url.to/apt/repo</replaceable> $(lsb_release -s -c) 4.0" > <filename>/etc/apt/sources.list.d/cloudstack.list</filename></programlisting>
|
||||
<programlisting><prompt>#</prompt> <command>apt-get</command> update </programlisting>
|
||||
</para>
|
||||
to make use of the APT repository. You can do this by adding a repository file
|
||||
under <filename>/etc/apt/sources.list.d</filename>. Use your preferred editor to
|
||||
create <filename>/etc/apt/sources.list.d/cloudstack.list</filename> with this
|
||||
line:</para>
|
||||
|
||||
<programlisting>deb http://<replaceable>server.url</replaceable>/cloudstack/repo binary/</programlisting>
|
||||
|
||||
<para>Now that you have the repository info in place, you'll want to run another
|
||||
update so that APT knows where to find the &PRODUCT; packages.</para>
|
||||
|
||||
<screen><command>$ sudo apt-get update</command></screen>
|
||||
|
||||
<para>You can now move on to the instructions under Install on Ubuntu.</para>
|
||||
|
||||
</section>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@
|
|||
<para>To configure CAStor:</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Install &PRODUCT; 4.0 by following the instructions given in the INSTALL.txt
|
||||
<para>Install &PRODUCT; 4.0.0-incubating by following the instructions given in the INSTALL.txt
|
||||
file.</para>
|
||||
<note>
|
||||
<para>You can use the S3 storage system in &PRODUCT; without setting up and installing the
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
under the License.
|
||||
-->
|
||||
<section id="changed-apicommands-4.0">
|
||||
<title>Changed API Commands in 4.0</title>
|
||||
<title>Changed API Commands in 4.0.0-incubating</title>
|
||||
<informaltable>
|
||||
<tgroup cols="2" align="left" colsep="1" rowsep="1">
|
||||
<colspec colwidth="1" colname="1" colnum="1"/>
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@
|
|||
<bookinfo id="cloudstack_all">
|
||||
<title>&PRODUCT; Complete Documentation</title>
|
||||
<productname>Apache CloudStack</productname>
|
||||
<productnumber>4.0</productnumber>
|
||||
<productnumber>4.0.0-incubating</productnumber>
|
||||
<edition>1</edition>
|
||||
<pubsnumber></pubsnumber>
|
||||
<abstract>
|
||||
|
|
@ -76,4 +76,4 @@
|
|||
<xi:include href="time-zones.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
<xi:include href="event-types.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
<xi:include href="alerts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
</book>
|
||||
</book>
|
||||
|
|
|
|||
|
|
@ -26,6 +26,6 @@
|
|||
<title>Adding a Cluster</title>
|
||||
<para>You need to tell &PRODUCT; about the hosts that it will manage. Hosts exist inside clusters, so before you begin adding hosts to the cloud, you must add at least one cluster.</para>
|
||||
<xi:include href="add-clusters-kvm-xenserver.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
<xi:include href="add-clusters-ovm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
<!-- <xi:include href="add-clusters-ovm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
|
||||
<xi:include href="add-clusters-vsphere.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -39,8 +39,9 @@
|
|||
</note>
|
||||
<section id="configure-package-repository-deb">
|
||||
<title>DEB package repository</title>
|
||||
<para>You can add a DEB package repository to your apt sources with the following commands. Please note that currently only packages for Ubuntu 12.04 (precise) are being build.</para>
|
||||
<programlisting language="Bash">echo "deb http://cloudstack.apt-get.eu/ubuntu $(lsb_release -s -c) 4.0" > /etc/apt/sources.list.d/cloudstack.list</programlisting>
|
||||
<para>You can add a DEB package repository to your apt sources with the following commands. Please note that currently only packages for Ubuntu 12.04.1 LTS (precise) are being build.</para>
|
||||
<para>Use your preferred editor and open (or create) <filename>/etc/apt/sources.list.d/cloudstack</filename>. Add the community provided repository to the file:</para>
|
||||
<programlisting>deb http://cloudstack.apt-get.eu/ubuntu precise 4.0</programlisting>
|
||||
<para>We now have to add the public key to the trusted keys.</para>
|
||||
<programlisting language="Bash"><prompt>#</prompt> <command>wget</command> -O - http://cloudstack.apt-get.eu/release.asc|apt-key add -</programlisting>
|
||||
<para>Now update your local apt cache.</para>
|
||||
|
|
|
|||
|
|
@ -24,6 +24,6 @@
|
|||
|
||||
<section id="create-template-from-snapshot">
|
||||
<title>Creating a Template from a Snapshot</title>
|
||||
<note><para>Not supported by Oracle VM</para></note>
|
||||
<!-- <note><para>Not supported by Oracle VM</para></note> -->
|
||||
<para>If you do not want to stop the VM in order to use the Create Template menu item (as described in <xref linkend="create-template-from-existing-vm"/>), you can create a template directly from any snapshot through the &PRODUCT; UI.</para>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -188,4 +188,4 @@
|
|||
<para>Click OK.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</section>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -44,6 +44,6 @@
|
|||
<listitem><para>Click Add Instance.</para></listitem>
|
||||
<listitem><para>Select ISO Boot, and follow the steps in the wizard.</para></listitem>
|
||||
<listitem><para>Click Submit and your VM will be created and started.</para></listitem>
|
||||
<listitem><para>(Oracle VM only) After ISO installation, the installer reboots into the operating system. Due to a known issue in OVM, the reboot will place the VM in the Stopped state. In the &PRODUCT; UI, detach the ISO from the VM (so that the VM will not boot from the ISO again), then click the Start button to restart the VM.</para></listitem>
|
||||
<!-- <listitem><para>(Oracle VM only) After ISO installation, the installer reboots into the operating system. Due to a known issue in OVM, the reboot will place the VM in the Stopped state. In the &PRODUCT; UI, detach the ISO from the VM (so that the VM will not boot from the ISO again), then click the Start button to restart the VM.</para></listitem> -->
|
||||
</orderedlist>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@
|
|||
<note><para>This procedure is different from moving disk volumes from one storage pool to another. See VM Storage Migration </para></note>
|
||||
<para>A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT; administrators and users can detach volumes from VMs and move them to other VMs.</para>
|
||||
<para>If the two VMs are in different clusters, and the volume is large, it may take several minutes for the volume to be moved to the new VM.</para>
|
||||
<para>If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para>
|
||||
<!-- <para>If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
|
||||
<orderedlist>
|
||||
<listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem>
|
||||
<listitem><para>In the left navigation bar, click Storage, and choose Volumes in Select View. Alternatively, if you know which VM the volume is attached to, you can click Instances, click the VM name, and click View Volumes.</para></listitem>
|
||||
|
|
|
|||
|
|
@ -28,10 +28,7 @@
|
|||
<emphasis role="bold">Multiple Hypervisor Support</emphasis>
|
||||
</para>
|
||||
<para>
|
||||
&PRODUCT; works with a variety of hypervisors. A single cloud deployment can contain multiple hypervisor implementations. You have the complete freedom to choose the right hypervisor for your workload.
|
||||
</para>
|
||||
<para>
|
||||
&PRODUCT; is designed to work with open source Xen and KVM hypervisors as well as enterprise-grade hypervisors such as Citrix XenServer, VMware vSphere, and Oracle VM (OVM). You can also provision “bare metal” hosts with no hypervisor (Beta feature. Untested in &PRODUCT; 3.0.x.)
|
||||
&PRODUCT; works with a variety of hypervisors, and a single cloud deployment can contain multiple hypervisor implementations. The current release of &PRODUCT; supports pre-packaged enterprise solutions like Citrix XenServer and VMware vSphere, as well as KVM or Xen running on Ubuntu or CentOS.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis role="bold">Massively Scalable Infrastructure Management</emphasis>
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
<section id="sect-source-gettingrelease">
|
||||
<title>Getting the release</title>
|
||||
<para>
|
||||
You can download the official &PRODUCT; 4.0.0 release from the
|
||||
You can download the latest &PRODUCT; release from the
|
||||
<ulink url="http://incubator.apache.org/cloudstack/downloads.html">
|
||||
Apache CloudStack project download page</ulink>.
|
||||
</para>
|
||||
|
|
|
|||
|
|
@ -22,10 +22,10 @@
|
|||
under the License.
|
||||
-->
|
||||
<section id="host-add-xenserver-kvm-ovm">
|
||||
<title>Adding a Host (XenServer, KVM, or OVM)</title>
|
||||
<para>XenServer, KVM, and Oracle VM (OVM) hosts can be added to a cluster at any time.</para>
|
||||
<title>Adding a Host (XenServer or KVM)</title>
|
||||
<para>XenServer and KVM hosts can be added to a cluster at any time.</para>
|
||||
<section>
|
||||
<title>Requirements for XenServer, KVM, and OVM Hosts</title>
|
||||
<title>Requirements for XenServer and KVM Hosts</title>
|
||||
<warning>
|
||||
<para>Make sure the hypervisor host does not have any VMs already running before you add it to
|
||||
&PRODUCT;.</para>
|
||||
|
|
@ -85,14 +85,14 @@
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
</section>
|
||||
<section>
|
||||
<title>OVM Host Additional Requirements</title>
|
||||
<!-- <section>
|
||||
<title>OVM Host Additional Requirements</title>
|
||||
<para>Before adding a used host in &PRODUCT;, as part of the cleanup procedure on the host, be
|
||||
sure to remove /etc/ovs-agent/db/.</para>
|
||||
</section>
|
||||
sure to remove /etc/ovs-agent/db/.</para>
|
||||
</section> -->
|
||||
</section>
|
||||
<section>
|
||||
<title>Adding a XenServer, KVM, or OVM Host</title>
|
||||
<title>Adding a XenServer or KVM Host</title>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>If you have not already done so, install the hypervisor software on the host. You will
|
||||
|
|
@ -130,8 +130,8 @@
|
|||
<para>Username. Usually root.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Password. This is the password for the user named above (from your XenServer, KVM,
|
||||
or OVM install).</para>
|
||||
<para>Password. This is the password for the user from your XenServer or KVM
|
||||
install).</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Host Tags (Optional). Any labels that you use to categorize hosts for ease of
|
||||
|
|
|
|||
|
|
@ -39,4 +39,4 @@
|
|||
</orderedlist>
|
||||
<xi:include href="host-add-xenserver-kvm-ovm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
<xi:include href="host-add-vsphere.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
</section>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -27,5 +27,5 @@
|
|||
<xi:include href="hypervisor-kvm-install-flow.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
<xi:include href="citrix-xenserver-installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
<xi:include href="vmware-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
<xi:include href="ovm-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||
</chapter>
|
||||
<!-- <xi:include href="ovm-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> -->
|
||||
</chapter>
|
||||
|
|
|
|||
|
|
@ -40,7 +40,6 @@
|
|||
<entry><para>VMware vSphere</para></entry>
|
||||
<entry><para>Citrix XenServer</para></entry>
|
||||
<entry><para>KVM</para></entry>
|
||||
<entry><para>Oracle VM</para></entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
|
@ -50,28 +49,24 @@
|
|||
<entry><para>VMDK</para></entry>
|
||||
<entry><para>VHD</para></entry>
|
||||
<entry><para>QCOW2</para></entry>
|
||||
<entry><para>RAW</para></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><para><emphasis role="bold">iSCSI support</emphasis></para></entry>
|
||||
<entry><para>VMFS</para></entry>
|
||||
<entry><para>Clustered LVM</para></entry>
|
||||
<entry><para>Yes, via Shared Mountpoint</para></entry>
|
||||
<entry><para>Yes, via OCFS2M</para></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><para><emphasis role="bold">Fiber Channel support</emphasis></para></entry>
|
||||
<entry><para>VMFS</para></entry>
|
||||
<entry><para>Yes, via Existing SR</para></entry>
|
||||
<entry><para>Yes, via Shared Mountpoint</para></entry>
|
||||
<entry><para>No</para></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><para><emphasis role="bold">NFS support</emphasis></para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
@ -79,7 +74,6 @@
|
|||
<entry><para>Y</para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
<entry><para>Y</para></entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
@ -87,7 +81,6 @@
|
|||
<entry><para>NFS and iSCSI</para></entry>
|
||||
<entry><para>NFS</para></entry>
|
||||
<entry><para>NFS</para></entry>
|
||||
<entry><para>No</para></entry>
|
||||
</row>
|
||||
|
||||
</tbody>
|
||||
|
|
@ -95,8 +88,8 @@
|
|||
</informaltable>
|
||||
<para>XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber Channel volumes and does not support over-provisioning in the hypervisor. The storage server itself, however, can support thin-provisioning. As a result the &PRODUCT; can still support storage over-provisioning by running on thin-provisioned storage volumes.</para>
|
||||
<para>KVM supports "Shared Mountpoint" storage. A shared mountpoint is a file system path local to each server in a given cluster. The path must be the same across all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is assumed to be a clustered filesystem such as OCFS2. In this case the &PRODUCT; does not attempt to mount or unmount the storage as is done with NFS. The &PRODUCT; requires that the administrator insure that the storage is available</para>
|
||||
<para>Oracle VM supports both iSCSI and NFS storage. When iSCSI is used with OVM, the &PRODUCT; administrator is responsible for setting up iSCSI on the host, including re-mounting the storage after the host recovers from a failure such as a network outage. With other hypervisors, &PRODUCT; takes care of mounting the iSCSI target on the host whenever it discovers a connection with an iSCSI server and unmounting the target when it discovers the connection is down.</para>
|
||||
<!-- <para>Oracle VM supports both iSCSI and NFS storage. When iSCSI is used with OVM, the &PRODUCT; administrator is responsible for setting up iSCSI on the host, including re-mounting the storage after the host recovers from a failure such as a network outage. With other hypervisors, &PRODUCT; takes care of mounting the iSCSI target on the host whenever it discovers a connection with an iSCSI server and unmounting the target when it discovers the connection is down.</para> -->
|
||||
<para>With NFS storage, &PRODUCT; manages the overprovisioning. In this case the global configuration parameter storage.overprovisioning.factor controls the degree of overprovisioning. This is independent of hypervisor type.</para>
|
||||
<para>Local storage is an option for primary storage for vSphere, XenServer, Oracle VM, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration.</para>
|
||||
<para>Local storage is an option for primary storage for vSphere, XenServer, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration.</para>
|
||||
<para>&PRODUCT; supports multiple primary storage pools in a Cluster. For example, you could provision 2 NFS servers in primary storage. Or you could provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the first approaches capacity.</para>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@
|
|||
<listitem><para>The destination host must be in the same cluster as the original host.</para></listitem>
|
||||
<listitem><para>The VM must not be using local disk storage.</para></listitem>
|
||||
<listitem><para>The destination host must have enough available capacity. If not, the VM will remain in the "migrating" state until memory becomes available.</para></listitem>
|
||||
<listitem><para>(OVM) If the VM is running on the OVM hypervisor, it must not have an ISO attached. Live migration of a VM with attached ISO is not supported in OVM.</para></listitem>
|
||||
<!-- <listitem><para>(OVM) If the VM is running on the OVM hypervisor, it must not have an ISO attached. Live migration of a VM with attached ISO is not supported in OVM.</para></listitem> -->
|
||||
</itemizedlist>
|
||||
<para>To manually live migrate a virtual machine</para>
|
||||
<orderedlist>
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@
|
|||
<listitem><para><xref linkend="hypervisor-kvm-requirements"/></para></listitem>
|
||||
<listitem><para><xref linkend="system-requirements-xenserver-hosts"/></para></listitem>
|
||||
<listitem><para><xref linkend="vmware-requirements"/></para></listitem>
|
||||
<listitem><para><xref linkend="ovm-requirements"/></para></listitem>
|
||||
<!-- <listitem><para><xref linkend="ovm-requirements"/></para></listitem> -->
|
||||
</itemizedlist>
|
||||
</section>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -25,4 +25,4 @@
|
|||
<section id="ovm-requirements">
|
||||
<title>System Requirements for OVM</title>
|
||||
<para>TODO</para>
|
||||
</section>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -22,8 +22,8 @@
|
|||
-->
|
||||
<section id="Features-of-the-Nicira-NVP-Plugin">
|
||||
<title>Features of the Nicira NVP Plugin</title>
|
||||
<para>In CloudStack release 4.0.x this plugin supports the Connectivity service. This service is responsible for creating Layer 2 networks supporting the networks created by Guests. In other words when an tennant creates a new network, instead of the traditional VLAN a logical network will be created by sending the appropriate calls to the Nicira NVP Controller.</para>
|
||||
<para>In CloudStack release 4.0.0-incubating this plugin supports the Connectivity service. This service is responsible for creating Layer 2 networks supporting the networks created by Guests. In other words when an tennant creates a new network, instead of the traditional VLAN a logical network will be created by sending the appropriate calls to the Nicira NVP Controller.</para>
|
||||
<para>The plugin has been tested with Nicira NVP versions 2.1.0, 2.2.0 and 2.2.1</para>
|
||||
<note><para>In CloudStack 4.0.x only the XenServer hypervisor is supported for use in combination with Nicira NVP</para></note>
|
||||
<note><para>In CloudStack 4.0.x the UI components for this plugin are not complete, configuration is done by sending commands to the API</para></note>
|
||||
</section>
|
||||
<note><para>In CloudStack 4.0.0-incubating only the XenServer hypervisor is supported for use in combination with Nicira NVP</para></note>
|
||||
<note><para>In CloudStack 4.0.0-incubating the UI components for this plugin are not complete, configuration is done by sending commands to the API</para></note>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@
|
|||
</author>
|
||||
<revdescription>
|
||||
<simplelist>
|
||||
<member>Documentation created for 4.0.x version of the NVP Plugin</member>
|
||||
<member>Documentation created for 4.0.0-incubating version of the NVP Plugin</member>
|
||||
</simplelist>
|
||||
</revdescription>
|
||||
</revision>
|
||||
|
|
|
|||
|
|
@ -1254,9 +1254,9 @@ Done restarting router(s).
|
|||
<listitem>
|
||||
<para>KVM : QCOW2</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<!-- <listitem>
|
||||
<para>OVM : RAW</para>
|
||||
</listitem>
|
||||
</listitem> -->
|
||||
</itemizedlist>
|
||||
</section>
|
||||
<section id="dedicated-ha-hosts">
|
||||
|
|
@ -2024,6 +2024,13 @@ Done restarting router(s).
|
|||
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
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
|
||||
<section id="runtime-behavior-of-primary-storage">
|
||||
<title>Runtime Behavior of Primary Storage</title>
|
||||
<para>Root volumes are created automatically when a virtual machine is created. Root volumes are deleted when the VM is destroyed. Data volumes can be created and dynamically attached to VMs (although, when the Oracle VM hypervisor is used, the VM must be stopped before an additional volume can be attached). Data volumes are not deleted when VMs are destroyed.</para>
|
||||
<para>Root volumes are created automatically when a virtual machine is created. Root volumes are deleted when the VM is destroyed. Data volumes can be created and dynamically attached to VMs. <!-- (although, when the Oracle VM hypervisor is used, the VM must be stopped before an additional volume can be attached)--> Data volumes are not deleted when VMs are destroyed.</para>
|
||||
<para>Administrators should monitor the capacity of primary storage devices and add additional primary storage as needed. See the Advanced Installation Guide.</para>
|
||||
<para>Administrators add primary storage to the system by creating a &PRODUCT; storage pool. Each storage pool is associated with a cluster.</para>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -32,8 +32,11 @@
|
|||
<para>Provide private IPs for the system in each pod and provision them in &PRODUCT;.</para>
|
||||
<para>For KVM and XenServer, the recommended number of private IPs per pod is one per host. If you expect a pod to grow, add enough private IPs now to accommodate the growth.</para>
|
||||
<para><emphasis role="bold">In a zone that uses advanced networking:</emphasis></para>
|
||||
<para>For vSphere with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required &PRODUCT; System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see Working with System Virtual Machines in the Administrator's Guide.</para>
|
||||
<para>For zones with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required &PRODUCT; System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see Working with System Virtual Machines in the Administrator's Guide.</para>
|
||||
<para>When advanced networking is being used, the number of private IP addresses available in each pod varies depending on which hypervisor is running on the nodes in that pod. Citrix XenServer and KVM use link-local addresses, which in theory provide more than 65,000 private IP addresses within the address block. As the pod grows over time, this should be more than enough for any reasonable number of hosts as well as IP addresses for guest virtual routers. VMWare ESXi, by contrast uses any administrator-specified subnetting scheme, and the typical administrator provides only 255 IPs per pod. Since these are shared by physical machines, the guest virtual router, and other entities, it is possible to run out of private IPs when scaling up a pod whose nodes are running ESXi.</para>
|
||||
<para>To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or more of the following techniques:</para>
|
||||
<para>TODO</para>
|
||||
<para>To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or both of the following techniques:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Specify a larger CIDR block for the subnet. A subnet mask with a /20 suffix will provide more than 4,000 IP addresses.</para></listitem>
|
||||
<listitem><para>Create multiple pods, each with its own subnet. For example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses.</para></listitem>
|
||||
</itemizedlist>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -59,10 +59,10 @@
|
|||
<entry><para>KVM</para></entry>
|
||||
<entry><para>QCOW2</para></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!-- <row>
|
||||
<entry><para>OVM</para></entry>
|
||||
<entry><para>RAW</para></entry>
|
||||
</row>
|
||||
</row> -->
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable></listitem>
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
|
||||
<section id="upload-template">
|
||||
<title>Uploading Templates</title>
|
||||
<note><para>If you are uploading a template that was created using vSphere Client, be sure the OVA file does not contain an ISO. If it does, the deployment of VMs from the template will fail.</para></note>
|
||||
<warning><title>vSphere Templates and ISOs</title><para>If you are uploading a template that was created using vSphere Client, be sure the OVA file does not contain an ISO. If it does, the deployment of VMs from the template will fail.</para></warning>
|
||||
<para>Templates are uploaded based on a URL. HTTP is the supported access protocol. Templates are frequently large files. You can optionally gzip them to decrease upload times.</para>
|
||||
<para>To upload a template:</para>
|
||||
<orderedlist>
|
||||
|
|
@ -39,7 +39,7 @@
|
|||
<itemizedlist>
|
||||
<listitem><para>If the operating system of the stopped VM is listed, choose it.</para></listitem>
|
||||
<listitem><para>If the OS type of the stopped VM is not listed, choose Other.</para>
|
||||
<note><para>Generally you should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other.</para></note></listitem>
|
||||
<note><para>You should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other.</para></note></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para><emphasis role="bold">Hypervisor</emphasis></para></listitem>
|
||||
|
|
|
|||
|
|
@ -39,4 +39,4 @@
|
|||
<xi:include href="added-API-commands.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
<xi:include href="added-error-codes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
||||
</section>
|
||||
</chapter>
|
||||
</chapter>
|
||||
|
|
|
|||
|
|
@ -25,8 +25,8 @@
|
|||
<section id="working-with-snapshots">
|
||||
<title>Working with Snapshots</title>
|
||||
<para>(Supported for the following hypervisors: <emphasis role="bold">XenServer</emphasis>, <emphasis role="bold">VMware vSphere</emphasis>, and <emphasis role="bold">KVM</emphasis>)</para>
|
||||
<para>&PRODUCT; supports snapshots of disk volumes. Snapshots are a point-in-time capture of virtual machine disks. Memory and CPU states are not captured. If you are using the Oracle VM hypervisor, you can not take snapshots, since OVM does not support them.</para>
|
||||
<para>Snapshots may be taken for volumes, including both root and data disks (except when the Oracle VM hypervisor is used, which does not support snapshots). The administrator places a limit on the number of stored snapshots per user. Users can create new volumes from the snapshot for recovery of particular files and they can create templates from snapshots to boot from a restored disk.</para>
|
||||
<para>&PRODUCT; supports snapshots of disk volumes. Snapshots are a point-in-time capture of virtual machine disks. Memory and CPU states are not captured. <!-- If you are using the Oracle VM hypervisor, you can not take snapshots, since OVM does not support them. --></para>
|
||||
<para>Snapshots may be taken for volumes, including both root and data disks. The administrator places a limit on the number of stored snapshots per user. Users can create new volumes from the snapshot for recovery of particular files and they can create templates from snapshots to boot from a restored disk.</para>
|
||||
<para>Users can create snapshots manually or by setting up automatic recurring snapshot policies. Users can also create disk volumes from snapshots, which may be attached to a VM like any other disk volume. Snapshots of both root disks and data disks are supported. However, &PRODUCT; does not currently support booting a VM from a recovered root disk. A disk recovered from snapshot of a root disk is treated as a regular data disk; the data on recovered disk can be accessed by attaching the disk to a VM.</para>
|
||||
<para>A completed snapshot is copied from primary storage to secondary storage, where it is stored until deleted or purged by newer snapshot.</para>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@
|
|||
<para>Volumes are created for a specific hypervisor type. A volume that has
|
||||
been attached to guest using one hypervisor type (e.g, XenServer) may not
|
||||
be attached to a guest that is using another hypervisor type (e.g.
|
||||
vSphere, Oracle VM, KVM). This is because the different hypervisors use
|
||||
vSphere, KVM). This is because the different hypervisors use
|
||||
different disk image formats.
|
||||
</para>
|
||||
<para>&PRODUCT; defines a volume as a unit of storage available to a guest
|
||||
|
|
|
|||
|
|
@ -1,5 +1,22 @@
|
|||
#!/bin/sh
|
||||
|
||||
# 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.
|
||||
|
||||
# An example hook script to prepare the commit log message.
|
||||
# Called by "git commit" with the name of the file that has the
|
||||
# commit message, followed by the description of the commit
|
||||
|
|
|
|||
|
|
@ -15,59 +15,42 @@
|
|||
# specific language governing permissions and limitations
|
||||
# under the License.
|
||||
|
||||
import pymysql
|
||||
import mysql
|
||||
import contextlib
|
||||
from mysql import connector
|
||||
from mysql.connector import errors
|
||||
from contextlib import closing
|
||||
import cloudstackException
|
||||
import sys
|
||||
import os
|
||||
import traceback
|
||||
|
||||
class dbConnection(object):
|
||||
def __init__(self, host="localhost", port=3306, user='cloud', passwd='cloud', db='cloud'):
|
||||
self.host = host
|
||||
self.port = port
|
||||
self.user = user
|
||||
self.user = str(user) #Workaround: http://bugs.mysql.com/?id=67306
|
||||
self.passwd = passwd
|
||||
self.database = db
|
||||
|
||||
try:
|
||||
self.db = pymysql.Connect(host=host, port=port, user=user, passwd=passwd, db=db)
|
||||
except:
|
||||
traceback.print_exc()
|
||||
raise cloudstackException.InvalidParameterException(sys.exc_info())
|
||||
|
||||
def __copy__(self):
|
||||
return dbConnection(self.host, self.port, self.user, self.passwd, self.database)
|
||||
|
||||
def close(self):
|
||||
try:
|
||||
self.db.close()
|
||||
except:
|
||||
pass
|
||||
|
||||
def execute(self, sql=None):
|
||||
def execute(self, sql=None, params=None):
|
||||
if sql is None:
|
||||
return None
|
||||
|
||||
|
||||
resultRow = []
|
||||
cursor = None
|
||||
try:
|
||||
# commit to restart the transaction, else we don't get fresh data
|
||||
self.db.commit()
|
||||
cursor = self.db.cursor()
|
||||
cursor.execute(sql)
|
||||
|
||||
result = cursor.fetchall()
|
||||
if result is not None:
|
||||
for r in result:
|
||||
resultRow.append(r)
|
||||
return resultRow
|
||||
except pymysql.MySQLError, e:
|
||||
raise cloudstackException.dbException("db Exception:%s"%e)
|
||||
except:
|
||||
raise cloudstackException.internalError(sys.exc_info())
|
||||
finally:
|
||||
if cursor is not None:
|
||||
cursor.close()
|
||||
|
||||
with contextlib.closing(mysql.connector.connect(host=self.host, port=self.port, user=self.user, password=self.passwd, db=self.database)) as conn:
|
||||
conn.autocommit = True
|
||||
with contextlib.closing(conn.cursor(buffered=True)) as cursor:
|
||||
cursor.execute(sql, params)
|
||||
try:
|
||||
result = cursor.fetchall()
|
||||
except errors.InterfaceError:
|
||||
#Raised on empty result - DML
|
||||
result = []
|
||||
if result:
|
||||
[resultRow.append(r) for r in result]
|
||||
|
||||
return resultRow
|
||||
|
||||
def executeSqlFromFile(self, fileName=None):
|
||||
if fileName is None:
|
||||
raise cloudstackException.InvalidParameterException("file can't not none")
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@
|
|||
# specific language governing permissions and limitations
|
||||
# under the License.
|
||||
|
||||
from distutils.core import setup
|
||||
from setuptools import setup
|
||||
from sys import version
|
||||
import sys
|
||||
|
||||
|
|
@ -37,7 +37,7 @@ setup(name="Marvin",
|
|||
packages=["marvin", "marvin.cloudstackAPI", "marvin.sandbox", "marvin.sandbox.advanced", "marvin.sandbox.basic"],
|
||||
license="LICENSE.txt",
|
||||
install_requires=[
|
||||
"pymysql",
|
||||
"mysql-connector-python",
|
||||
"paramiko",
|
||||
"nose",
|
||||
"unittest-xml-reporting"
|
||||
|
|
|
|||
|
|
@ -1484,6 +1484,12 @@
|
|||
isHidden: true,
|
||||
isBoolean: true
|
||||
},
|
||||
associatePublicIP: {
|
||||
label: 'Associate IP',
|
||||
isBoolean: true,
|
||||
isHidden: true,
|
||||
dependsOn: 'service.Lb.elasticLbCheckbox'
|
||||
},
|
||||
"service.Lb.lbIsolationDropdown": {
|
||||
label: 'label.LB.isolation',
|
||||
isHidden: true,
|
||||
|
|
@ -1604,6 +1610,12 @@
|
|||
} else {
|
||||
inputData['conservemode'] = false;
|
||||
}
|
||||
|
||||
if (inputData['associatePublicIP'] == 'on') {
|
||||
inputData['associatePublicIP'] = true;
|
||||
} else {
|
||||
inputData['associatePublicIP'] = false;
|
||||
}
|
||||
|
||||
// Make service provider map
|
||||
var serviceProviderIndex = 0;
|
||||
|
|
|
|||
Loading…
Reference in New Issue