This is an automated email from the ASF dual-hosted git repository.
paul_a pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/master by this push:
new dbca62f documentation for selecting a pod, cluster or host during VM
deploy (#15)
dbca62f is described below
commit dbca62fea44699aba1206e991fdc68273da30169
Author: Henko <[email protected]>
AuthorDate: Wed Apr 24 10:07:34 2019 +0200
documentation for selecting a pod, cluster or host during VM deploy (#15)
* documentation for selecting a pod, cluster or host during VM deployment /
start
* Address gabriel's comments
---
source/adminguide/virtual_machines.rst | 10 ++++++++--
source/releasenotes/api-changes.rst | 14 ++++++++++++--
2 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/source/adminguide/virtual_machines.rst
b/source/adminguide/virtual_machines.rst
index 61b5d10..5b1038c 100644
--- a/source/adminguide/virtual_machines.rst
+++ b/source/adminguide/virtual_machines.rst
@@ -185,7 +185,7 @@ To create a VM from a template:
#. Click Add Instance.
-#. Select a zone.
+#. Select a zone. Admin users will have the option to select a pod, cluster or
host.
#. Select a template, then follow the steps in the wizard. For more
information about how the templates came to be in this list, see
@@ -215,7 +215,7 @@ To create a VM from an ISO:
#. Click Add Instance.
-#. Select a zone.
+#. Select a zone. Admin users will have the option to select a pod, cluster or
host.
#. Select ISO Boot, and follow the steps in the wizard.
@@ -263,6 +263,8 @@ Once a VM instance is created, you can stop, restart, or
delete it as
needed. In the CloudStack UI, click Instances, select the VM, and use
the Stop, Start, Reboot, and Destroy buttons.
+When starting a VM, admin users have the option to specify a pod, cluster, or
host.
+
Assigning VMs to Hosts
----------------------
@@ -288,6 +290,10 @@ There are several ways:
allocation places a guest on each host in a round-robin fashion. This
may yield better performance to the guests in some cases.
+- Admin users preferences. Administrators have the option to specify a
+ pod, cluster, or host to run the VM in. CloudStack will then select
+ a host within the given infrastructure.
+
- End user preferences. Users can not control exactly which host will
run a given VM instance, but they can specify a zone for the VM.
CloudStack is then restricted to allocating the VM only to one of the
diff --git a/source/releasenotes/api-changes.rst
b/source/releasenotes/api-changes.rst
index c2cea13..1da163f 100644
--- a/source/releasenotes/api-changes.rst
+++ b/source/releasenotes/api-changes.rst
@@ -618,6 +618,9 @@ Parameters Changed API Commands
| | - ``datadiskofferinglist``
(optional) |
| | - ``dhcpoptionsnetworklist``
(optional) |
| | - ``macaddress`` (optional)
|
+| | - ``podid`` (optional)
|
+| | - ``clusterid`` (optional)
|
+| | - ``hostid`` (optional)
|
| |
|
+---------------------------------------------+--------------------------------------------------------------------------------+
| ``listVlanIpRanges`` | **Response:**
|
@@ -1019,5 +1022,12 @@ Parameters Changed API Commands
| | - ``volumeids``
|
| |
|
+---------------------------------------------+--------------------------------------------------------------------------------+
-
-
+| ``startVirtualMachine`` | **Request:**
|
+| |
|
+| | *New Parameters:*
|
+| |
|
+| | - ``podid`` (optional)
|
+| | - ``clusterid`` (optional)
|
+| | - ``hostid`` (optional)
|
+| |
|
++---------------------------------------------+--------------------------------------------------------------------------------+
