http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/virtual_machines.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/virtual_machines.pot
b/source/locale/pot/virtual_machines.pot
index 32a1751..8e3fc9d 100644
--- a/source/locale/pot/virtual_machines.pot
+++ b/source/locale/pot/virtual_machines.pot
@@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
-# Copyright (C)
+# Copyright (C) 2016, Apache Software Foundation
# This file is distributed under the same license as the Apache CloudStack
Administration Documentation package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <l...@li.org>\n"
@@ -17,197 +17,158 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
#: ../../virtual_machines.rst:18
-# 825181279d9643c3ae9e1a485765f79a
msgid "Working with Virtual Machines"
msgstr ""
#: ../../virtual_machines.rst:21
-# 8ef9955cc01742fb833f6f4cb20ddc40
msgid "About Working with Virtual Machines"
msgstr ""
#: ../../virtual_machines.rst:23
-# 5dfc79c076ae4bcf9b78cbc7e7998fb1
msgid "CloudStack provides administrators with complete control over the
lifecycle of all guest VMs executing in the cloud. CloudStack provides several
guest management operations for end users and administrators. VMs may be
stopped, started, rebooted, and destroyed."
msgstr ""
#: ../../virtual_machines.rst:28
-# a74753cd5a1e4e87b2b25bb214d76583
msgid "Guest VMs have a name and group. VM names and groups are opaque to
CloudStack and are available for end users to organize their VMs. Each VM can
have three names for use in different contexts. Only two of these names can be
controlled by the user:"
msgstr ""
#: ../../virtual_machines.rst:33
-# 33b7dd1035fe468788852c131410d355
msgid "Instance name â a unique, immutable ID that is generated by
CloudStack and can not be modified by the user. This name conforms to the
requirements in IETF RFC 1123."
msgstr ""
#: ../../virtual_machines.rst:37
-# f1b72ed931524f89a7d072ed361a635e
msgid "Display name â the name displayed in the CloudStack web UI. Can be
set by the user. Defaults to instance name."
msgstr ""
#: ../../virtual_machines.rst:40
-# adc0efb3ff154603a38bf9294009ac65
msgid "Name â host name that the DHCP server assigns to the VM. Can be set
by the user. Defaults to instance name"
msgstr ""
#: ../../virtual_machines.rst:44
-# 14d2256532ea4ba9ab19bed35890856a
msgid "You can append the display name of a guest VM to its internal name. For
more information, see `âAppending a Display Name to the Guest VMâs Internal
Nameâ <#appending-a-display-name-to-the-guest-vms-internal-name>`_."
msgstr ""
#: ../../virtual_machines.rst:48
-# a8d661456c4f45b28ad427c44e9b6325
msgid "Guest VMs can be configured to be Highly Available (HA). An HA-enabled
VM is monitored by the system. If the system detects that the VM is down, it
will attempt to restart the VM, possibly on a different host. For more
information, see HA-Enabled Virtual Machines on"
msgstr ""
#: ../../virtual_machines.rst:53
-# 5305c3fec9d94b62aa5980618331557e
msgid "Each new VM is allocated one public IP address. When the VM is started,
CloudStack automatically creates a static NAT between this public IP address
and the private IP address of the VM."
msgstr ""
#: ../../virtual_machines.rst:57
-# 587dd3d141fc46bca48b617989e96f59
msgid "If elastic IP is in use (with the NetScaler load balancer), the IP
address initially allocated to the new VM is not marked as elastic. The user
must replace the automatically configured IP with a specifically acquired
elastic IP, and set up the static NAT mapping between this new IP and the guest
VMâs private IP. The VMâs original IP address is then released and returned
to the pool of available public IPs. Optionally, you can also decide not to
allocate a public IP to a VM in an EIP-enabled Basic zone. For more information
on Elastic IP, see `âAbout Elastic IPâ
<networking2.html#about-elastic-ip>`_."
msgstr ""
#: ../../virtual_machines.rst:67
-# 6fbeb0da9ef448f98d0a7a11b1032be6
msgid "CloudStack cannot distinguish a guest VM that was shut down by the user
(such as with the âshutdownâ command in Linux) from a VM that shut down
unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudStack
will restart it. To shut down an HA-enabled VM, you must go through the
CloudStack UI or API."
msgstr ""
#: ../../virtual_machines.rst:75
-# 9787aabb3dc94e8db7a5de0c51ea7443
msgid "Best Practices for Virtual Machines"
msgstr ""
#: ../../virtual_machines.rst:77
-# 6372fe37d9ed4beeb1424ae97b03ad24
msgid "For VMs to work as expected and provide excellent service, follow these
guidelines."
msgstr ""
#: ../../virtual_machines.rst:82
-# d2a792bb33c2418bba1e90839b5208d4
msgid "Monitor VMs for Max Capacity"
msgstr ""
#: ../../virtual_machines.rst:84
-# aaa155f7b055496592fb19179ed93f73
msgid "The CloudStack administrator should monitor the total number of VM
instances in each cluster, and disable allocation to the cluster if the total
is approaching the maximum that the hypervisor can handle. Be sure to leave a
safety margin to allow for the possibility of one or more hosts failing, which
would increase the VM load on the other hosts as the VMs are automatically
redeployed. Consult the documentation for your chosen hypervisor to find the
maximum permitted number of VMs per host, then use CloudStack global
configuration settings to set this as the default limit. Monitor the VM
activity in each cluster at all times. Keep the total number of VMs below a
safe level that allows for the occasional host failure. For example, if there
are N hosts in the cluster, and you want to allow for one host in the cluster
to be down at any given time, the total number of VM instances you can permit
in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches
this num
ber of VMs, use the CloudStack UI to disable allocation of more VMs to the
cluster."
msgstr ""
#: ../../virtual_machines.rst:103
-# e6554027f7f9466a8a5ab12bbbf30fb9
msgid "Install Required Tools and Drivers"
msgstr ""
#: ../../virtual_machines.rst:105
-# 6b07dcd845a944ea872a6ace009f7f24
msgid "Be sure the following are installed on each VM:"
msgstr ""
#: ../../virtual_machines.rst:107
-# 31fe2e3e61ec4b15865970eafecc35df
msgid "For XenServer, install PV drivers and Xen tools on each VM. This will
enable live migration and clean guest shutdown. Xen tools are required in order
for dynamic CPU and RAM scaling to work."
msgstr ""
#: ../../virtual_machines.rst:111
-# 59c6618b482a4e8590293c7da8aaf7ef
msgid "For vSphere, install VMware Tools on each VM. This will enable console
view to work properly. VMware Tools are required in order for dynamic CPU and
RAM scaling to work."
msgstr ""
#: ../../virtual_machines.rst:115
-# 0054a653c9ee4d008cb5fff30bcb3de8
msgid "To be sure that Xen tools or VMware Tools is installed, use one of the
following techniques:"
msgstr ""
#: ../../virtual_machines.rst:118
-# 183593c0142745a49f4f2a3791981e31
msgid "Create each VM from a template that already has the tools installed;
or,"
msgstr ""
#: ../../virtual_machines.rst:121
-# 4ad9dec1226046d48a5dba3598abbf0a
msgid "When registering a new template, the administrator or user can indicate
whether tools are installed on the template. This can be done through the UI or
using the updateTemplate API; or,"
msgstr ""
#: ../../virtual_machines.rst:125
-# 3a12a213c40345018c066a0ec37e65a9
msgid "If a user deploys a virtual machine with a template that does not have
Xen tools or VMware Tools, and later installs the tools on the VM, then the
user can inform CloudStack using the updateVirtualMachine API. After installing
the tools and updating the virtual machine, stop and start the VM."
msgstr ""
#: ../../virtual_machines.rst:133
-# b7a0169d017a496787e38b9e50311a88
msgid "VM Lifecycle"
msgstr ""
#: ../../virtual_machines.rst:135
-# 0af797cf30df4ac984c7b8d11ede977e
msgid "Virtual machines can be in the following states:"
msgstr ""
#: ../../virtual_machines.rst:137
-# f5d2991885b4440f8c7062a60633f065
msgid "|basic-deployment.png|"
msgstr ""
#: ../../virtual_machines.rst:139
-# 4c2d3ebcce3744b481035492578b6e3c
msgid "Once a virtual machine is destroyed, it cannot be recovered. All the
resources used by the virtual machine will be reclaimed by the system. This
includes the virtual machineâs IP address."
msgstr ""
#: ../../virtual_machines.rst:143
-# 08c95a701e5348e789bd295aa7819d86
msgid "A stop will attempt to gracefully shut down the operating system, which
typically involves terminating all the running applications. If the operation
system cannot be stopped, it will be forcefully terminated. This has the same
effect as pulling the power cord to a physical machine."
msgstr ""
#: ../../virtual_machines.rst:149
-# 6d5fb2afbc1e44ad842f052187cc201f
msgid "A reboot is a stop followed by a start."
msgstr ""
#: ../../virtual_machines.rst:151
-# eb78f755807e4fe59ff45bc534fa6dc5
msgid "CloudStack preserves the state of the virtual machine hard disk until
the machine is destroyed."
msgstr ""
#: ../../virtual_machines.rst:154
-# e18941c1f49b40d4ae53034763c41e57
msgid "A running virtual machine may fail because of hardware or network
issues. A failed virtual machine is in the down state."
msgstr ""
#: ../../virtual_machines.rst:157
-# 73bd5337e5854464a320f36cca3d4964
msgid "The system places the virtual machine into the down state if it does
not receive the heartbeat from the hypervisor for three minutes."
msgstr ""
#: ../../virtual_machines.rst:160
-# a45ff69a534b47189b4457ff2d058d8c
msgid "The user can manually restart the virtual machine from the down state."
msgstr ""
#: ../../virtual_machines.rst:162
-# 42d0a445aab2404abad8ce54e6ff5947
msgid "The system will start the virtual machine from the down state
automatically if the virtual machine is marked as HA-enabled."
msgstr ""
#: ../../virtual_machines.rst:167
-# fdeb58579e7749fe88bdf405f79049e5
msgid "Creating VMs"
msgstr ""
#: ../../virtual_machines.rst:169
-# 7453d7d0a14e4a9dab16d5580766c5d5
msgid "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."
msgstr ""
#: ../../virtual_machines.rst:175
-# 3edf15d4b2054f90ae481e9bde143346
msgid "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."
msgstr ""
#: ../../virtual_machines.rst:180
-# e3cf740a72c247ea8cdb5ff298a2e7b3
msgid "To create a VM from a template:"
msgstr ""
@@ -215,1397 +176,1438 @@ msgstr ""
#: ../../virtual_machines.rst:212
#: ../../virtual_machines.rst:330
#: ../../virtual_machines.rst:366
-# 6b4fb12f7826449389052e48b175bf9a
-# 1c346e18dafd4ac7977a7dc98d85926c
-# 4d63920f853642a68b92f2632d3a1ba1
-# d667b7df24994fc4ac857e47436efd5d
msgid "Log in to the CloudStack UI as an administrator or user."
msgstr ""
#: ../../virtual_machines.rst:184
#: ../../virtual_machines.rst:214
#: ../../virtual_machines.rst:368
-# 243b4d8b914d49d19dd68312aae2042a
-# fbbc9105a1f14883918e0460b902a681
-# 74fc4567c9104ff0ae51ec0d88dc5006
msgid "In the left navigation bar, click Instances."
msgstr ""
#: ../../virtual_machines.rst:186
#: ../../virtual_machines.rst:216
-# be1be45993694cb6ab943a5c229ac71e
-# 7d1b7b4f15c349c68567df62e225bc34
msgid "Click Add Instance."
msgstr ""
#: ../../virtual_machines.rst:188
#: ../../virtual_machines.rst:218
-# 64202b2c542d459596118bf9dd4ad508
-# 7f1cbee620c946a88f43e9b6c8f1e9bf
msgid "Select a zone."
msgstr ""
#: ../../virtual_machines.rst:190
-# a0aa0f810b974edcb1d8f305c1b24a5d
msgid "Select a template, then follow the steps in the wizard. For more
information about how the templates came to be in this list, see `*Working with
Templates* <templates.html>`_."
msgstr ""
#: ../../virtual_machines.rst:194
-# 33bbf5e131484a929c10053278adddde
msgid "Be sure that the hardware you have allows starting the selected service
offering."
msgstr ""
#: ../../virtual_machines.rst:197
#: ../../virtual_machines.rst:222
-# 9a01eecf26a748e198056df4f7e9b825
-# 82109b204e5841308ff5e74b12cf24a4
msgid "Click Submit and your VM will be created and started."
msgstr ""
#: ../../virtual_machines.rst:200
-# 7a2965e6d5004b7088a5e5bc18da649c
msgid "For security reason, the internal name of the VM is visible only to the
root admin."
msgstr ""
#: ../../virtual_machines.rst:203
-# c19e66233eaa4d00b5b615550ebc0c11
msgid "To create a VM from an ISO:"
msgstr ""
#: ../../virtual_machines.rst:206
-# ff3d83c8dc1b40baab04b8c1bcfe3619
msgid "(XenServer) Windows VMs running on XenServer require PV drivers, which
may be provided in the template or added after the VM is created. The PV
drivers are necessary for essential management functions such as mounting
additional volumes and ISO images, live migration, and graceful shutdown."
msgstr ""
#: ../../virtual_machines.rst:220
-# aceacbbcfec4422e939ff1ed89aa25c5
msgid "Select ISO Boot, and follow the steps in the wizard."
msgstr ""
#: ../../virtual_machines.rst:226
-# a843dc7f749c44d89ba116d3c6af89f8
msgid "Accessing VMs"
msgstr ""
#: ../../virtual_machines.rst:228
-# 0bf035db01dd401abc60fc76e71330ba
msgid "Any user can access their own virtual machines. The administrator can
access all VMs running in the cloud."
msgstr ""
#: ../../virtual_machines.rst:231
#: ../../virtual_machines.rst:555
-# ff40a54bdc2e4f3f8b310d37998c096b
-# b719e6aa6218441b864dbd9dbb664b20
msgid "To access a VM through the CloudStack UI:"
msgstr ""
#: ../../virtual_machines.rst:233
#: ../../virtual_machines.rst:557
-#: ../../virtual_machines.rst:618
-#: ../../virtual_machines.rst:792
-#: ../../virtual_machines.rst:820
-# 72fdf34366e84d53a902f30170e96826
-# 3b5b89a3e29346439a79e6c9625ab11a
-# 5d3ec5e17ef1449a85064c70381209dc
-# 151cdfe9cd414184908d5b1c15cc7de9
-# 995bd5571b2446418ec4a6f27a17fe5f
+#: ../../virtual_machines.rst:620
+#: ../../virtual_machines.rst:794
+#: ../../virtual_machines.rst:822
msgid "Log in to the CloudStack UI as a user or admin."
msgstr ""
#: ../../virtual_machines.rst:235
-# c09833ddb4424c4e82d2b49397dbf82e
msgid "Click Instances, then click the name of a running VM."
msgstr ""
#: ../../virtual_machines.rst:237
-# 7276130f1e014d969cbd9246b1310121
msgid "Click the View Console button |console-icon.png|."
msgstr ""
#: ../../virtual_machines.rst:239
-# c06df9b367c1493a908523e863cade69
msgid "To access a VM directly over the network:"
msgstr ""
#: ../../virtual_machines.rst:241
-# 3a9997d1c0444c66b00f908de1b14f74
msgid "The VM must have some port open to incoming traffic. For example, in a
basic zone, a new VM might be assigned to a security group which allows
incoming traffic. This depends on what security group you picked when creating
the VM. In other cases, you can open a port by setting up a port forwarding
policy. See `âIP Forwarding and Firewallingâ
<networking2.html#ip-forwarding-and-firewalling>`_."
msgstr ""
#: ../../virtual_machines.rst:248
-# aa1d9ea00c0f47d58155e9aa67793a80
msgid "If a port is open but you can not access the VM using ssh, itâs
possible that ssh is not already enabled on the VM. This will depend on whether
ssh is enabled in the template you picked when creating the VM. Access the VM
through the CloudStack UI and enable ssh on the machine using the commands for
the VMâs operating system."
msgstr ""
#: ../../virtual_machines.rst:254
-# af42226ae2f845c4ae39472cd44d62cf
msgid "If the network has an external firewall device, you will need to create
a firewall rule to allow access. See `âIP Forwarding and Firewallingâ
<networking2.html#ip-forwarding-and-firewalling>`_."
msgstr ""
#: ../../virtual_machines.rst:260
-# 334cb66ea0fd46fab55d62d6c94401cc
msgid "Stopping and Starting VMs"
msgstr ""
#: ../../virtual_machines.rst:262
-# 194b6682b53b4c028e9387e57f318392
msgid "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."
msgstr ""
#: ../../virtual_machines.rst:268
-# 3475020a222a4190b9e4e184a4be143c
msgid "Assigning VMs to Hosts"
msgstr ""
#: ../../virtual_machines.rst:270
-# ab04e4134ad1499abbfb64970cd8d83b
msgid "At any point in time, each virtual machine instance is running on a
single host. How does CloudStack determine which host to place a VM on? There
are several ways:"
msgstr ""
#: ../../virtual_machines.rst:274
-# c9fcda8e47454c1b9ccdd115dc618ffb
msgid "Automatic default host allocation. CloudStack can automatically pick
the most appropriate host to run each virtual machine."
msgstr ""
#: ../../virtual_machines.rst:277
-# 13722d82fe934c8fbe47baadf772e4b3
msgid "Instance type preferences. CloudStack administrators can specify that
certain hosts should have a preference for particular types of guest instances.
For example, an administrator could state that a host should have a preference
to run Windows guests. The default host allocator will attempt to place guests
of that OS type on such hosts first. If no such host is available, the
allocator will place the instance wherever there is sufficient physical
capacity."
msgstr ""
#: ../../virtual_machines.rst:285
-# a32cedb1c3d54276bafa87b47914776e
msgid "Vertical and horizontal allocation. Vertical allocation consumes all
the resources of a given host before allocating any guests on a second host.
This reduces power consumption in the cloud. Horizontal allocation places a
guest on each host in a round-robin fashion. This may yield better performance
to the guests in some cases."
msgstr ""
#: ../../virtual_machines.rst:291
-# cc5699db1af34f3a9b499307c558a058
msgid "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 hosts in that zone."
msgstr ""
#: ../../virtual_machines.rst:296
-# 0411284295194622b05a0cb1879eeb76
msgid "Host tags. The administrator can assign tags to hosts. These tags can
be used to specify which host a VM should use. The CloudStack administrator
decides whether to define host tags, then create a service offering using those
tags and offer it to the user."
msgstr ""
#: ../../virtual_machines.rst:301
-# ead4cb40fadd4eefa3f8eeddf36bea8e
msgid "Affinity groups. By defining affinity groups and assigning VMs to them,
the user or administrator can influence (but not dictate) which VMs should run
on separate hosts. This feature is to let users specify that certain VMs won't
be on the same host."
msgstr ""
#: ../../virtual_machines.rst:306
-# 475f207be88542b496285e35e6edb937
msgid "CloudStack also provides a pluggable interface for adding new
allocators. These custom allocators can provide any policy the administrator
desires."
msgstr ""
#: ../../virtual_machines.rst:312
-# 838c2813c99f4ea89cb67e8b2ff25abd
msgid "Affinity Groups"
msgstr ""
#: ../../virtual_machines.rst:314
-# d72b6ebfff7246118fbc4df220e6f966
msgid "By defining affinity groups and assigning VMs to them, the user or
administrator can influence (but not dictate) which VMs should run on separate
hosts. This feature is to let users specify that VMs with the same âhost
anti-affinityâ type wonât be on the same host. This serves to increase
fault tolerance. If a host fails, another VM offering the same service (for
example, hosting the user's website) is still up and running on another host."
msgstr ""
#: ../../virtual_machines.rst:322
-# 7dad3924b6fe49e9b9e6ed13a6316bbf
msgid "The scope of an affinity group is per user account."
msgstr ""
#: ../../virtual_machines.rst:326
-# 537f3770162d4c7db20724e2cd3a6d25
msgid "Creating a New Affinity Group"
msgstr ""
#: ../../virtual_machines.rst:328
-# 89ec84e3b1004702a136fe33ae40a620
msgid "To add an affinity group:"
msgstr ""
#: ../../virtual_machines.rst:332
#: ../../virtual_machines.rst:382
#: ../../virtual_machines.rst:397
-# 2e4c181542d24eceadbedafacef6a048
-# 129e5d65a94748d49cc72d49901d7982
-# bfe6c54e9b1d4b95b230d06a783465c2
msgid "In the left navigation bar, click Affinity Groups."
msgstr ""
#: ../../virtual_machines.rst:334
-# 2d49709c41b24dcfa6cbec72f9655ecb
msgid "Click Add affinity group. In the dialog box, fill in the following
fields:"
msgstr ""
#: ../../virtual_machines.rst:337
-# 8f2541aa578d480ab600f234860b710f
msgid "Name. Give the group a name."
msgstr ""
#: ../../virtual_machines.rst:339
-# 283fc43838584136ada4a8670741a62f
msgid "Description. Any desired text to tell more about the purpose of the
group."
msgstr ""
#: ../../virtual_machines.rst:342
-# 6ad15d35202c4aa3829229be0b4dc5a3
msgid "Type. The only supported type shipped with CloudStack is Host
Anti-Affinity. This indicates that the VMs in this group should avoid being
placed on the same host with each other. If you see other types in this list,
it means that your installation of CloudStack has been extended with customized
affinity group plugins."
msgstr ""
#: ../../virtual_machines.rst:351
-# 9dd18a72cf94423295b7f4e16ebdd474
msgid "Assign a New VM to an Affinity Group"
msgstr ""
#: ../../virtual_machines.rst:353
-# f986290eacc04fcd88cddb44e54dd110
msgid "To assign a new VM to an affinity group:"
msgstr ""
#: ../../virtual_machines.rst:355
-# b7ecd6311df24770b2f5ff16290be095
msgid "Create the VM as usual, as described in `âCreating VMsâ
<virtual_machines.html#creating-vms>`_. In the Add Instance wizard, there is a
new Affinity tab where you can select the affinity group."
msgstr ""
#: ../../virtual_machines.rst:362
-# d887ac9c84494254beaf5d7c2d1d8b17
msgid "Change Affinity Group for an Existing VM"
msgstr ""
#: ../../virtual_machines.rst:364
-# ac05d8cab3d84c0fb5fecc7ff5be7a41
msgid "To assign an existing VM to an affinity group:"
msgstr ""
#: ../../virtual_machines.rst:370
-# 406004d08a994c7e83f19eb8d3d5ccb4
msgid "Click the name of the VM you want to work with."
msgstr ""
#: ../../virtual_machines.rst:372
-# 5198d04fabab4aba81bb176cafd9cd5f
msgid "Stop the VM by clicking the Stop button."
msgstr ""
#: ../../virtual_machines.rst:374
-# d7c213c32fa64651beb6d71b29a2f881
msgid "Click the Change Affinity button. |change-affinity-button.png|"
msgstr ""
#: ../../virtual_machines.rst:378
-# 7964ffac44554385887c85ac33410324
msgid "View Members of an Affinity Group"
msgstr ""
#: ../../virtual_machines.rst:380
-# 60958f4621bd45d68c4c4e5ff8e6166b
msgid "To see which VMs are currently assigned to a particular affinity group:"
msgstr ""
#: ../../virtual_machines.rst:384
#: ../../virtual_machines.rst:399
-# 44277c6e70cc49f5a0262172b42602cd
-# 84c34fd8f1024bc3b3b89c6074d25602
msgid "Click the name of the group you are interested in."
msgstr ""
#: ../../virtual_machines.rst:386
-# d621ae0b24c54f108a31c5dc8cf05476
msgid "Click View Instances. The members of the group are listed."
msgstr ""
#: ../../virtual_machines.rst:388
-# 43f372265bc14aa89389bbc7b9584816
msgid "From here, you can click the name of any VM in the list to access all
its details and controls."
msgstr ""
#: ../../virtual_machines.rst:393
-# c126741a86364834b153814dff481a58
msgid "Delete an Affinity Group"
msgstr ""
#: ../../virtual_machines.rst:395
-# 41b2a9676116417a9cc26ddecd8e35c0
msgid "To delete an affinity group:"
msgstr ""
#: ../../virtual_machines.rst:401
-# 97c32e0a3b4d4a039f0167b916626e38
msgid "Click Delete."
msgstr ""
#: ../../virtual_machines.rst:403
-# 2f1e052c0a0441988e9ccb2459b64996
msgid "Any VM that is a member of the affinity group will be disassociated
from the group. The former group members will continue to run normally on the
current hosts, but if the VM is restarted, it will no longer follow the host
allocation rules from its former affinity group."
msgstr ""
#: ../../virtual_machines.rst:411
-# 1500b2cdf2f8433f9dc55740099c7554
msgid "Virtual Machine Snapshots"
msgstr ""
#: ../../virtual_machines.rst:413
-#: ../../virtual_machines.rst:643
-# 352168175d0f45c7944fb134e5e1ccb0
-# f1ff6b7e77974160b7eb0e268b6c8adf
+#: ../../virtual_machines.rst:645
msgid "(Supported on VMware and XenServer)"
msgstr ""
#: ../../virtual_machines.rst:415
-# 4b76741f3c964e48b09015a19ac9ffe6
msgid "In addition to the existing CloudStack ability to snapshot individual
VM volumes, you can take a VM snapshot to preserve all the VM's data volumes as
well as (optionally) its CPU/memory state. This is useful for quick restore of
a VM. For example, you can snapshot a VM, then make changes such as software
upgrades. If anything goes wrong, simply restore the VM to its previous state
using the previously saved VM snapshot."
msgstr ""
#: ../../virtual_machines.rst:423
-# 9ea94fa6d9804e22af343c5c65a0362d
msgid "The snapshot is created using the hypervisor's native snapshot
facility. The VM snapshot includes not only the data volumes, but optionally
also whether the VM is running or turned off (CPU state) and the memory
contents. The snapshot is stored in CloudStack's primary storage."
msgstr ""
#: ../../virtual_machines.rst:428
-# b710a2e6c248420bb55ebfa8f0f376dc
msgid "VM snapshots can have a parent/child relationship. Each successive
snapshot of the same VM is the child of the snapshot that came before it. Each
time you take an additional snapshot of the same VM, it saves only the
differences between the current state of the VM and the state stored in the
most recent previous snapshot. The previous snapshot becomes a parent, and the
new snapshot is its child. It is possible to create a long chain of these
parent/child snapshots, which amount to a \"redo\" record leading from the
current state of the VM back to the original."
msgstr ""
#: ../../virtual_machines.rst:438
-# efe6658a42c34ba1badb3bb03008f9f0
msgid "If you need more information about VM snapshots on VMware, check out
the VMware documentation and the VMware Knowledge Base, especially
`Understanding virtual machine snapshots
<http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180>`_."
msgstr ""
#: ../../virtual_machines.rst:445
-# 8fb9c61d831b4840801c19c568c3e2f7
msgid "Limitations on VM Snapshots"
msgstr ""
#: ../../virtual_machines.rst:447
-# b40a26e614ff482b83dd6fe7ca66a097
msgid "If a VM has some stored snapshots, you can't attach new volume to the
VM or delete any existing volumes. If you change the volumes on the VM, it
would become impossible to restore the VM snapshot which was created with the
previous volume structure. If you want to attach a volume to such a VM, first
delete its snapshots."
msgstr ""
#: ../../virtual_machines.rst:453
-# 137adaa8ad304bad8e6a62a539a5b277
msgid "VM snapshots which include both data volumes and memory can't be kept
if you change the VM's service offering. Any existing VM snapshots of this type
will be discarded."
msgstr ""
#: ../../virtual_machines.rst:457
-# 9890e43dc8174a959a93587c2843f753
msgid "You can't make a VM snapshot at the same time as you are taking a
volume snapshot."
msgstr ""
#: ../../virtual_machines.rst:460
-# 0ffbf8b4539648a4884ee457c3ab1cb1
msgid "You should use only CloudStack to create VM snapshots on hosts managed
by CloudStack. Any snapshots that you make directly on the hypervisor will not
be tracked in CloudStack."
msgstr ""
#: ../../virtual_machines.rst:466
-# 77f6cb8f4c0f41fcb04fe4aa2c2f5268
msgid "Configuring VM Snapshots"
msgstr ""
#: ../../virtual_machines.rst:468
-# 8582f7496ba340e7b18f0ec535fc74c1
msgid "The cloud administrator can use global configuration variables to
control the behavior of VM snapshots. To set these variables, go through the
Global Settings area of the CloudStack UI."
msgstr ""
#: ../../virtual_machines.rst:472
-# f9f9fa5a5bf040cf942989a479a5e690
msgid "Configuration Setting Name"
msgstr ""
#: ../../virtual_machines.rst:474
-# 68ee9c1c4d5a4d0b85ee63309d7b1db0
msgid "Description"
msgstr ""
#: ../../virtual_machines.rst:476
-# 85763ceb28de4f0eaca494db0a967117
msgid "vmsnapshots.max"
msgstr ""
#: ../../virtual_machines.rst:478
-# 7466c6685f504780a8c5d77c5d580374
msgid "The maximum number of VM snapshots that can be saved for any given
virtual machine in the cloud. The total possible number of VM snapshots in the
cloud is (number of VMs) \\* vmsnapshots.max. If the number of snapshots for
any VM ever hits the maximum, the older ones are removed by the snapshot
expunge job."
msgstr ""
#: ../../virtual_machines.rst:484
-# 2fd939410c2b4b3aa8b3003ab8a3b968
msgid "vmsnapshot.create.wait"
msgstr ""
#: ../../virtual_machines.rst:486
-# 375a0959e9c94eb1a423b278ae046b5b
msgid "Number of seconds to wait for a snapshot job to succeed before
declaring failure and issuing an error."
msgstr ""
#: ../../virtual_machines.rst:491
-# 2b92af396f6c475a81e3dd289b5b2058
msgid "Using VM Snapshots"
msgstr ""
#: ../../virtual_machines.rst:493
-# 936e0bc234f649d98911b973d2a89f24
msgid "To create a VM snapshot using the CloudStack UI:"
msgstr ""
#: ../../virtual_machines.rst:495
-# 7cd076f83efb4c1bbf3fd895f87582e8
msgid "Log in to the CloudStack UI as a user or administrator."
msgstr ""
#: ../../virtual_machines.rst:497
-# 79e76d457cf54a80bf3e15e93c930b60
msgid "Click Instances."
msgstr ""
#: ../../virtual_machines.rst:499
-# 271888c8e7844949b68a79c940659c7b
msgid "Click the name of the VM you want to snapshot."
msgstr ""
#: ../../virtual_machines.rst:501
-# e60b0597ab2c4b37b9c1b6e585208f39
msgid "Click the Take VM Snapshot button. |VMSnapshotButton.png|"
msgstr ""
#: ../../virtual_machines.rst:504
-# 516b8188c37544fe9289100fa8fd6f81
msgid "If a snapshot is already in progress, then clicking this button will
have no effect."
msgstr ""
#: ../../virtual_machines.rst:507
-# 3af8f23237d44f6a82ff3805d8748f9b
msgid "Provide a name and description. These will be displayed in the VM
Snapshots list."
msgstr ""
#: ../../virtual_machines.rst:510
-# 213a0335d6b44dc3a98d11a064dc6168
msgid "(For running VMs only) If you want to include the VM's memory in the
snapshot, click the Memory checkbox. This saves the CPU and memory state of the
virtual machine. If you don't check this box, then only the current state of
the VM disk is saved. Checking this box makes the snapshot take longer."
msgstr ""
#: ../../virtual_machines.rst:516
-# d45f3edd0bc741a7a60bc61f1687caae
msgid "Quiesce VM: check this box if you want to quiesce the file system on
the VM before taking the snapshot. Not supported on XenServer when used with
CloudStack-provided primary storage."
msgstr ""
#: ../../virtual_machines.rst:520
-# fe21f13b62b746c7a13b2f7f85a6eaa9
msgid "When this option is used with CloudStack-provided primary storage, the
quiesce operation is performed by the underlying hypervisor (VMware is
supported). When used with another primary storage vendor's plugin, the quiesce
operation is provided according to the vendor's implementation."
msgstr ""
#: ../../virtual_machines.rst:526
-#: ../../virtual_machines.rst:635
-#: ../../virtual_machines.rst:808
-#: ../../virtual_machines.rst:951
-#: ../../virtual_machines.rst:975
-# 2a6c32cefec74407bd7fbe5e305ad9fc
-# a8e7b2f2b1c94ee9ab5aacd3929d2b84
-# cd457f5e102e42109f716c58cae05fee
-# 2226bef2616a496e93a295e437d134ec
-# 48260fa4b2a8429582628ee0a4834f18
+#: ../../virtual_machines.rst:637
+#: ../../virtual_machines.rst:810
+#: ../../virtual_machines.rst:953
+#: ../../virtual_machines.rst:977
msgid "Click OK."
msgstr ""
#: ../../virtual_machines.rst:528
-# f4d9b9197aca4868ab4d46cfeaeeeb8d
msgid "To delete a snapshot or restore a VM to the state saved in a particular
snapshot:"
msgstr ""
#: ../../virtual_machines.rst:531
-# 36f6cf98d55c41459202b6750b7eb7f4
msgid "Navigate to the VM as described in the earlier steps."
msgstr ""
#: ../../virtual_machines.rst:533
-# bf91c94f8979476a930e9dbf513be4d4
msgid "Click View VM Snapshots."
msgstr ""
#: ../../virtual_machines.rst:535
-# e7ccaab839314560b552b6071fc14e64
msgid "In the list of snapshots, click the name of the snapshot you want to
work with."
msgstr ""
#: ../../virtual_machines.rst:538
-# 8e39335e75044ff99ab9e0def4fdc7d3
msgid "Depending on what you want to do:"
msgstr ""
#: ../../virtual_machines.rst:540
-# 1992a3d840bc470fabd250937c4de81e
msgid "To delete the snapshot, click the Delete button. |delete-button.png|"
msgstr ""
#: ../../virtual_machines.rst:542
-# 00f5fcea682d428c9a9e195edb1178e9
msgid "To revert to the snapshot, click the Revert button. |revert-vm.png|"
msgstr ""
#: ../../virtual_machines.rst:545
-# d31395bcdf554ce6a1057725cfec443b
msgid "VM snapshots are deleted automatically when a VM is destroyed. You
don't have to manually delete the snapshots in this case."
msgstr ""
#: ../../virtual_machines.rst:550
-# b68606a2ccc14896810536c55cfc1b43
msgid "Changing the VM Name, OS, or Group"
msgstr ""
#: ../../virtual_machines.rst:552
-# c3a4b62362fc4863a6506f6a5e3187de
msgid "After a VM is created, you can modify the display name, operating
system, and the group it belongs to."
msgstr ""
#: ../../virtual_machines.rst:559
-#: ../../virtual_machines.rst:620
-#: ../../virtual_machines.rst:794
-#: ../../virtual_machines.rst:822
-#: ../../virtual_machines.rst:967
-# 72447d94968d48569debc5b7e37e4e80
-# 635b0652817c46e8929098fb5425c79b
-# edcc32c2db4948f7b0702e1fec2c46dd
-# af3dab76cece4fbfa032b786f5efe55f
-# 19861b8d6dbc4928b12763a78bf07383
+#: ../../virtual_machines.rst:622
+#: ../../virtual_machines.rst:796
+#: ../../virtual_machines.rst:824
+#: ../../virtual_machines.rst:969
msgid "In the left navigation, click Instances."
msgstr ""
#: ../../virtual_machines.rst:561
-# b339e4730d0445bebdcb106a5c75c2f4
msgid "Select the VM that you want to modify."
msgstr ""
#: ../../virtual_machines.rst:563
-#: ../../virtual_machines.rst:627
-# 304e46f42670493198568fd5f0ff4ee9
-# 7fdd96b1f7e0497fb108cb28b45a1d3c
+#: ../../virtual_machines.rst:629
msgid "Click the Stop button to stop the VM. |StopButton.png|"
msgstr ""
#: ../../virtual_machines.rst:565
-# 8b84a60389bf4387933672f32d30340e
msgid "Click Edit. |EditButton.png|"
msgstr ""
#: ../../virtual_machines.rst:567
-# f5ce6fcba1ca478e9bd1598907c1a601
msgid "Make the desired changes to the following:"
msgstr ""
#: ../../virtual_machines.rst:569
-# 96da85f1c1db4d90b6131a4e7bbe1267
msgid "**Display name**: Enter a new display name if you want to change the
name of the VM."
msgstr ""
#: ../../virtual_machines.rst:572
-# b2eb919b8d15426a86942e811b6b785a
msgid "**OS Type**: Select the desired operating system."
msgstr ""
#: ../../virtual_machines.rst:574
-# 963531001c6f471fae769294df407de4
msgid "**Group**: Enter the group name for the VM."
msgstr ""
#: ../../virtual_machines.rst:576
-#: ../../virtual_machines.rst:691
-# 1f8f9ed119ca43b291afa2ae2b572532
-# acdd7ec88c4b4a27a7b9ade935e17aad
+#: ../../virtual_machines.rst:693
msgid "Click Apply."
msgstr ""
#: ../../virtual_machines.rst:580
-# 35efc08bc7314a2a83b202b6bfd078c6
msgid "Appending a Display Name to the Guest VMâs Internal Name"
msgstr ""
#: ../../virtual_machines.rst:582
-# 090483f924564a9d8180f7df880f4066
msgid "Every guest VM has an internal name. The host uses the internal name to
identify the guest VMs. CloudStack gives you an option to provide a guest VM
with a display name. You can set this display name as the internal name so that
the vCenter can use it to identify the guest VM. A new global parameter,
vm.instancename.flag, has now been added to achieve this functionality."
msgstr ""
#: ../../virtual_machines.rst:589
-# f1544ed6d7c34d8ebadbc2726fd7edb9
msgid "The default format of the internal name is
i-<user\\_id>-<vm\\_id>-<instance.name>, where instance.name is a global
parameter. However, If vm.instancename.flag is set to true, and if a display
name is provided during the creation of a guest VM, the display name is
appended to the internal name of the guest VM on the host. This makes the
internal name format as i-<user\\_id>-<vm\\_id>-<displayName>. The default
value of vm.instancename.flag is set to false. This feature is intended to make
the correlation between instance names and internal names easier in large data
center deployments."
msgstr ""
#: ../../virtual_machines.rst:599
-# fa48ed23ffd24df4a02ee5f2167670e9
msgid "The following table explains how a VM name is displayed in different
scenarios."
msgstr ""
-#: ../../virtual_machines.rst:603
-# 76ff8c667a8c480fb21958db7dd65d12
+#: ../../virtual_machines.rst:605
msgid "User-Provided Display Name"
msgstr ""
-#: ../../virtual_machines.rst:603
-# 77b3d04a25244f7b88843f76b0269874
+#: ../../virtual_machines.rst:605
msgid "vm.instancename.flag"
msgstr ""
-#: ../../virtual_machines.rst:603
-# eb539380b01a4ba7abe6fab6cbef8d37
+#: ../../virtual_machines.rst:605
msgid "Hostname on the VM"
msgstr ""
-#: ../../virtual_machines.rst:603
-# 44a68176f9334f3d893063ea88a1880e
+#: ../../virtual_machines.rst:605
msgid "Name on vCenter"
msgstr ""
-#: ../../virtual_machines.rst:603
-# 09d5fe54336843e99505c1bd9d7c24c9
+#: ../../virtual_machines.rst:605
msgid "Internal Name"
msgstr ""
-#: ../../virtual_machines.rst:605
#: ../../virtual_machines.rst:607
-# 8a2a30cd89b8470ab636c82eea18e3a4
-# 8c02dc549daa4804be4ee3b3bf8216a7
+#: ../../virtual_machines.rst:609
msgid "Yes"
msgstr ""
-#: ../../virtual_machines.rst:605
-#: ../../virtual_machines.rst:606
-# 854c972116cd4ffea1dd8e5be0d72b55
-# 2d6b531677a8463b806c81b61c640ad8
+#: ../../virtual_machines.rst:607
+#: ../../virtual_machines.rst:608
msgid "True"
msgstr ""
-#: ../../virtual_machines.rst:605
#: ../../virtual_machines.rst:607
-# e24020ac7abe425a8fc5ae02e4464a87
-# 1eaa0ac4785f44bf90d042a044d9500f
+#: ../../virtual_machines.rst:609
msgid "Display name"
msgstr ""
-#: ../../virtual_machines.rst:605
-#: ../../virtual_machines.rst:605
-# da8b1b08fbf24753a7ad71dc4c6e910a
-# b909f46baf824afb95db14b2c7a3628a
+#: ../../virtual_machines.rst:607
+#: ../../virtual_machines.rst:607
msgid "i-<user\\_id>-<vm\\_id>-displayName"
msgstr ""
-#: ../../virtual_machines.rst:606
#: ../../virtual_machines.rst:608
-# fe84676df63e465ab7918b5f44790a34
-# 799a550bf2024c8db25a267cd0eac622
+#: ../../virtual_machines.rst:610
msgid "No"
msgstr ""
-#: ../../virtual_machines.rst:606
#: ../../virtual_machines.rst:608
-# 2f6abcbb57e24820b71d94a8d721a901
-# 05c2b0965dab4221a022ca3f4d1fb71e
+#: ../../virtual_machines.rst:610
msgid "UUID"
msgstr ""
-#: ../../virtual_machines.rst:606
-#: ../../virtual_machines.rst:606
-#: ../../virtual_machines.rst:607
-#: ../../virtual_machines.rst:607
#: ../../virtual_machines.rst:608
#: ../../virtual_machines.rst:608
-# 5179011192fa4530bf1aa6561ba03e80
-# 0e4881cabf544619b6ed3f98b666fa4d
-# 923b87aaf25d404cb843c35fde7e8abf
-# 14cf566f26974c38b4ceaa39a9c10a2b
-# 5351204fc9aa4a09ac443444dcb12cf5
-# 1b26f9393c914e4bbc0f6099ee278a0e
+#: ../../virtual_machines.rst:609
+#: ../../virtual_machines.rst:609
+#: ../../virtual_machines.rst:610
+#: ../../virtual_machines.rst:610
msgid "i-<user\\_id>-<vm\\_id>-<instance.name>"
msgstr ""
-#: ../../virtual_machines.rst:607
-#: ../../virtual_machines.rst:608
-# 882c61362e02473eb3d26c71fc8a1d93
-# 2e62c668c7b74882a7c5518dd4e345b7
+#: ../../virtual_machines.rst:609
+#: ../../virtual_machines.rst:610
msgid "False"
msgstr ""
-#: ../../virtual_machines.rst:613
-# c1aad1317c774f3cb8be7a171d4c7615
+#: ../../virtual_machines.rst:615
msgid "Changing the Service Offering for a VM"
msgstr ""
-#: ../../virtual_machines.rst:615
-# aa826a1e593e4934b4bd9a30bd004c64
+#: ../../virtual_machines.rst:617
msgid "To upgrade or downgrade the level of compute resources available to a
virtual machine, you can change the VM's compute offering."
msgstr ""
-#: ../../virtual_machines.rst:622
-# 8c522d8ff0c341f08389ff47a300b9be
+#: ../../virtual_machines.rst:624
msgid "Choose the VM that you want to work with."
msgstr ""
-#: ../../virtual_machines.rst:624
-# 0efe6503c5934cb0b193cabcb06131e0
+#: ../../virtual_machines.rst:626
msgid "(Skip this step if you have enabled dynamic VM scaling; see
:ref:`cpu-and-memory-scaling`.)"
msgstr ""
-#: ../../virtual_machines.rst:629
-# 8a714661de844774afa81e0071868b59
+#: ../../virtual_machines.rst:631
msgid "Click the Change Service button. |ChangeServiceButton.png|"
msgstr ""
-#: ../../virtual_machines.rst:631
-# 83f39b159c464727b6fccf6e6b055c0e
+#: ../../virtual_machines.rst:633
msgid "The Change service dialog box is displayed."
msgstr ""
-#: ../../virtual_machines.rst:633
-# c981bd6e1e7f49bab3deb9b83f0477f6
+#: ../../virtual_machines.rst:635
msgid "Select the offering you want to apply to the selected VM."
msgstr ""
-#: ../../virtual_machines.rst:641
-# a01d7307691b4520a87be0d9d9b9da2d
+#: ../../virtual_machines.rst:643
msgid "CPU and Memory Scaling for Running VMs"
msgstr ""
-#: ../../virtual_machines.rst:645
-# ab0e9786b026430a9847f2f68311aeb3
+#: ../../virtual_machines.rst:647
msgid "It is not always possible to accurately predict the CPU and RAM
requirements when you first deploy a VM. You might need to increase these
resources at any time during the life of a VM. You can dynamically modify CPU
and RAM levels to scale up these resources for a running VM without incurring
any downtime."
msgstr ""
-#: ../../virtual_machines.rst:651
-# 115161eb80b3499bacb45dfdfebee485
+#: ../../virtual_machines.rst:653
msgid "Dynamic CPU and RAM scaling can be used in the following cases:"
msgstr ""
-#: ../../virtual_machines.rst:653
-# 30297090e50d4dde9f897f9a136fe4f6
+#: ../../virtual_machines.rst:655
msgid "User VMs on hosts running VMware and XenServer."
msgstr ""
-#: ../../virtual_machines.rst:655
-# 6232185457af46168206dcb77fbe3d5a
+#: ../../virtual_machines.rst:657
msgid "System VMs on VMware."
msgstr ""
-#: ../../virtual_machines.rst:657
-# f6a39632a5fc44fc95fe18b95ec76dca
+#: ../../virtual_machines.rst:659
msgid "VMware Tools or XenServer Tools must be installed on the virtual
machine."
msgstr ""
-#: ../../virtual_machines.rst:660
-# 3a9ff2ea379947d1a7d14452ee5a9f23
+#: ../../virtual_machines.rst:662
msgid "The new requested CPU and RAM values must be within the constraints
allowed by the hypervisor and the VM operating system."
msgstr ""
-#: ../../virtual_machines.rst:663
-# 5110926c89cb47f6b2f174d9b7fd2074
+#: ../../virtual_machines.rst:665
msgid "New VMs that are created after the installation of CloudStack 4.2 can
use the dynamic scaling feature. If you are upgrading from a previous version
of CloudStack, your existing VMs created with previous versions will not have
the dynamic scaling capability unless you update them using the following
procedure."
msgstr ""
-#: ../../virtual_machines.rst:671
-# 1ad181d6d7c7496e95ae7d8940fdae5e
+#: ../../virtual_machines.rst:673
msgid "Updating Existing VMs"
msgstr ""
-#: ../../virtual_machines.rst:673
-# 869cd5d508b846d8bac2af633484f301
+#: ../../virtual_machines.rst:675
msgid "If you are upgrading from a previous version of CloudStack, and you
want your existing VMs created with previous versions to have the dynamic
scaling capability, update the VMs using the following steps:"
msgstr ""
-#: ../../virtual_machines.rst:677
-# 11e41c992a6545bca58c3d47b712fc40
+#: ../../virtual_machines.rst:679
msgid "Make sure the zone-level setting enable.dynamic.scale.vm is set to
true. In the left navigation bar of the CloudStack UI, click Infrastructure,
then click Zones, click the zone you want, and click the Settings tab."
msgstr ""
-#: ../../virtual_machines.rst:682
-# 62c28d859ce4495393ca05ebe80feab9
+#: ../../virtual_machines.rst:684
msgid "Install Xen tools (for XenServer hosts) or VMware Tools (for VMware
hosts) on each VM if they are not already installed."
msgstr ""
-#: ../../virtual_machines.rst:685
-# d20322e380d44022b1ff5c61fdb66462
+#: ../../virtual_machines.rst:687
msgid "Stop the VM."
msgstr ""
-#: ../../virtual_machines.rst:687
-# 7fb4a5e90f7240faa3517081515db067
+#: ../../virtual_machines.rst:689
msgid "Click the Edit button."
msgstr ""
-#: ../../virtual_machines.rst:689
-# e27c8efe5a804069964feebad14fc869
+#: ../../virtual_machines.rst:691
msgid "Click the Dynamically Scalable checkbox."
msgstr ""
-#: ../../virtual_machines.rst:693
-# cfbb1778b1b04d149bb2c2bb69c274d3
+#: ../../virtual_machines.rst:695
msgid "Restart the VM."
msgstr ""
-#: ../../virtual_machines.rst:697
-# f11c788c7fd447179dd19538674fb81c
+#: ../../virtual_machines.rst:699
msgid "Configuring Dynamic CPU and RAM Scaling"
msgstr ""
-#: ../../virtual_machines.rst:699
-# 30af79a24d8f48a1b834110d8374abbc
+#: ../../virtual_machines.rst:701
msgid "To configure this feature, use the following new global configuration
variables:"
msgstr ""
-#: ../../virtual_machines.rst:702
-# 5a2816315adb4870943cb43b6d0cf99c
+#: ../../virtual_machines.rst:704
msgid "enable.dynamic.scale.vm: Set to True to enable the feature. By default,
the feature is turned off."
msgstr ""
-#: ../../virtual_machines.rst:705
-# cdeb9f1cb4df4b029610a510842cc284
+#: ../../virtual_machines.rst:707
msgid "scale.retry: How many times to attempt the scaling operation. Default =
2."
msgstr ""
-#: ../../virtual_machines.rst:710
-# 07decccd4eb04199817b30945867ed27
+#: ../../virtual_machines.rst:712
msgid "How to Dynamically Scale CPU and RAM"
msgstr ""
-#: ../../virtual_machines.rst:712
-# ae889fadf36342a6a037fb765a54fd59
+#: ../../virtual_machines.rst:714
msgid "To modify the CPU and/or RAM capacity of a virtual machine, you need to
change the compute offering of the VM to a new compute offering that has the
desired CPU and RAM values. You can use the same steps described above in
`âChanging the Service Offering for a VMâ
<#changing-the-service-offering-for-a-vm>`_, but skip the step where you stop
the virtual machine. Of course, you might have to create a new compute offering
first."
msgstr ""
-#: ../../virtual_machines.rst:720
-# 4ad82ed62390433a83075a6fe291e6c6
+#: ../../virtual_machines.rst:722
msgid "When you submit a dynamic scaling request, the resources will be scaled
up on the current host if possible. If the host does not have enough resources,
the VM will be live migrated to another host in the same cluster. If there is
no host in the cluster that can fulfill the requested level of CPU and RAM, the
scaling operation will fail. The VM will continue to run as it was before."
msgstr ""
-#: ../../virtual_machines.rst:729
-# 04a78ffb0e8a4995a6fbbf8870ef3c01
+#: ../../virtual_machines.rst:731
msgid "Limitations"
msgstr ""
-#: ../../virtual_machines.rst:731
-# 4d4543f814604671a8582fd47d1298ca
+#: ../../virtual_machines.rst:733
msgid "You can not do dynamic scaling for system VMs on XenServer."
msgstr ""
-#: ../../virtual_machines.rst:733
-# 0c3b91b5ecc54cb1b79f79eea7129458
+#: ../../virtual_machines.rst:735
msgid "CloudStack will not check to be sure that the new CPU and RAM levels
are compatible with the OS running on the VM."
msgstr ""
-#: ../../virtual_machines.rst:736
-# c8b490e8cfa64c6c992a761349ffcec9
+#: ../../virtual_machines.rst:738
msgid "When scaling memory or CPU for a Linux VM on VMware, you might need to
run scripts in addition to the other steps mentioned above. For more
information, see `Hot adding memory in Linux (1012764)
<http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012764>`_
in the VMware Knowledge Base."
msgstr ""
-#: ../../virtual_machines.rst:742
-# 4e112807f7f146ccb7683bafe9845553
+#: ../../virtual_machines.rst:744
msgid "(VMware) If resources are not available on the current host, scaling up
will fail on VMware because of a known issue where CloudStack and vCenter
calculate the available capacity differently. For more information, see
`https://issues.apache.org/jira/browse/CLOUDSTACK-1809
<https://issues.apache.org/jira/browse/CLOUDSTACK-1809>`_."
msgstr ""
-#: ../../virtual_machines.rst:748
-# eed3ea4ba4134de1b4cb819e07cb8326
+#: ../../virtual_machines.rst:750
msgid "On VMs running Linux 64-bit and Windows 7 32-bit operating systems, if
the VM is initially assigned a RAM of less than 3 GB, it can be dynamically
scaled up to 3 GB, but not more. This is due to a known issue with these
operating systems, which will freeze if an attempt is made to dynamically scale
from less than 3 GB to more than 3 GB."
msgstr ""
-#: ../../virtual_machines.rst:756
-# 0f66f02496244365a1fc127038eafca0
+#: ../../virtual_machines.rst:758
msgid "Resetting the Virtual Machine Root Volume on Reboot"
msgstr ""
-#: ../../virtual_machines.rst:758
-# 63185701fdb845c78448a80722e1e1f9
+#: ../../virtual_machines.rst:760
msgid "For secure environments, and to ensure that VM state is not persisted
across reboots, you can reset the root disk. For more information, see
`âReset VM to New Root Disk on Rebootâ
<storage.html#reset-vm-to-new-root-disk-on-reboot>`_."
msgstr ""
-#: ../../virtual_machines.rst:765
-# 66018bd4d29d47f5b9921b2b638bd9e5
+#: ../../virtual_machines.rst:767
msgid "Moving VMs Between Hosts (Manual Live Migration)"
msgstr ""
-#: ../../virtual_machines.rst:767
-# 4a11ec0f0f7849af900329d21eb5021a
+#: ../../virtual_machines.rst:769
msgid "The CloudStack administrator can move a running VM from one host to
another without interrupting service to users or going into maintenance mode.
This is called manual live migration, and can be done under the following
conditions:"
msgstr ""
-#: ../../virtual_machines.rst:772
-# f7d30be3c9c04c2890163879415fbec7
+#: ../../virtual_machines.rst:774
msgid "The root administrator is logged in. Domain admins and users can not
perform manual live migration of VMs."
msgstr ""
-#: ../../virtual_machines.rst:775
-# 17e5f9d4b5d849c395dc3660e836ea8c
+#: ../../virtual_machines.rst:777
msgid "The VM is running. Stopped VMs can not be live migrated."
msgstr ""
-#: ../../virtual_machines.rst:777
-# 948845ad74164fee9ba6899a995747ff
+#: ../../virtual_machines.rst:779
msgid "The destination host must have enough available capacity. If not, the
VM will remain in the \"migrating\" state until memory becomes available."
msgstr ""
-#: ../../virtual_machines.rst:781
-# 926ce179048d440ba2bea6731af74b85
+#: ../../virtual_machines.rst:783
msgid "(KVM) The VM must not be using local disk storage. (On XenServer and
VMware, VM live migration with local disk is enabled by CloudStack support for
XenMotion and vMotion.)"
msgstr ""
-#: ../../virtual_machines.rst:785
-# 7afc45cd0fd64406bf6773ae8ca01061
+#: ../../virtual_machines.rst:787
msgid "(KVM) The destination host must be in the same cluster as the original
host. (On XenServer and VMware, VM live migration from one cluster to another
is enabled by CloudStack support for XenMotion and vMotion.)"
msgstr ""
-#: ../../virtual_machines.rst:790
-# 5b314d24029f4c3b8005118729a96b8a
+#: ../../virtual_machines.rst:792
msgid "To manually live migrate a virtual machine"
msgstr ""
-#: ../../virtual_machines.rst:796
-# 1e1e47dac41d499993b564e4a93cb2d3
+#: ../../virtual_machines.rst:798
msgid "Choose the VM that you want to migrate."
msgstr ""
-#: ../../virtual_machines.rst:798
-# 761a3094e3774e94a810eb219c96c394
+#: ../../virtual_machines.rst:800
msgid "Click the Migrate Instance button. |Migrateinstance.png|"
msgstr ""
-#: ../../virtual_machines.rst:800
-# fd690eecd191485bb7d1b4908411a5cc
+#: ../../virtual_machines.rst:802
msgid "From the list of suitable hosts, choose the one to which you want to
move the VM."
msgstr ""
-#: ../../virtual_machines.rst:804
-# 726aae3ee8924808ba550a28342fc0e5
+#: ../../virtual_machines.rst:806
msgid "If the VM's storage has to be migrated along with the VM, this will be
noted in the host list. CloudStack will take care of the storage migration for
you."
msgstr ""
-#: ../../virtual_machines.rst:812
-# 8f08330a7d1e42caaf5ef765aa58882a
+#: ../../virtual_machines.rst:814
msgid "Deleting VMs"
msgstr ""
-#: ../../virtual_machines.rst:814
-# c3d724719a8246f193d97c4f0d121699
+#: ../../virtual_machines.rst:816
msgid "Users can delete their own virtual machines. A running virtual machine
will be abruptly stopped before it is deleted. Administrators can delete any
virtual machines."
msgstr ""
-#: ../../virtual_machines.rst:818
-# 7ce9ae8ec54a41f9a717fdf87bd9c144
+#: ../../virtual_machines.rst:820
msgid "To delete a virtual machine:"
msgstr ""
-#: ../../virtual_machines.rst:824
-# e404b64388f74a71bbfc6af41ccd3ff1
+#: ../../virtual_machines.rst:826
msgid "Choose the VM that you want to delete."
msgstr ""
-#: ../../virtual_machines.rst:826
-# 2d8231a2d7c149b796ed88861d1bb909
+#: ../../virtual_machines.rst:828
msgid "Click the Destroy Instance button. |Destroyinstance.png|"
msgstr ""
-#: ../../virtual_machines.rst:830
-# e060074ca29143089e33cdd841b6e53c
+#: ../../virtual_machines.rst:832
msgid "Working with ISOs"
msgstr ""
-#: ../../virtual_machines.rst:832
-# 49e588f8f3d3457396167bfe47840a9c
+#: ../../virtual_machines.rst:834
msgid "CloudStack supports ISOs and their attachment to guest VMs. An ISO is a
read-only file that has an ISO/CD-ROM style file system. Users can upload their
own ISOs and mount them on their guest VMs."
msgstr ""
-#: ../../virtual_machines.rst:836
-# 43da1c69da0e4ff3ba3867e9061ad9c4
+#: ../../virtual_machines.rst:838
msgid "ISOs are uploaded based on a URL. HTTP is the supported protocol. Once
the ISO is available via HTTP specify an upload URL such as
http://my.web.server/filename.iso.";
msgstr ""
-#: ../../virtual_machines.rst:840
-# 646b8bd2384245229f23171a7a8d7712
+#: ../../virtual_machines.rst:842
msgid "ISOs may be public or private, like templates.ISOs are not
hypervisor-specific. That is, a guest on vSphere can mount the exact same image
that a guest on KVM can mount."
msgstr ""
-#: ../../virtual_machines.rst:844
-# 3d98a7d5d5ef47d5b8a0ccafaa66e0e7
+#: ../../virtual_machines.rst:846
msgid "ISO images may be stored in the system and made available with a
privacy level similar to templates. ISO images are classified as either
bootable or not bootable. A bootable ISO image is one that contains an OS
image. CloudStack allows a user to boot a guest VM off of an ISO image. Users
can also attach ISO images to guest VMs. For example, this enables installing
PV drivers into Windows. ISO images are not hypervisor-specific."
msgstr ""
-#: ../../virtual_machines.rst:854
-# 8d9568801830478a848ccdac420a263f
+#: ../../virtual_machines.rst:856
msgid "Adding an ISO"
msgstr ""
-#: ../../virtual_machines.rst:856
-# ba8d1a29acc24d7ca0da86abbc13d3d2
+#: ../../virtual_machines.rst:858
msgid "To make additional operating system or other software available for use
with guest VMs, you can add an ISO. The ISO is typically thought of as an
operating system image, but you can also add ISOs for other types of software,
such as desktop applications that you want to be installed as part of a
template."
msgstr ""
-#: ../../virtual_machines.rst:862
-# 79227c9ef0904022a147fb56ff1f7530
+#: ../../virtual_machines.rst:864
msgid "Log in to the CloudStack UI as an administrator or end user."
msgstr ""
-#: ../../virtual_machines.rst:864
-# 0241367a6d3f4783a3b774447b3e7ba8
+#: ../../virtual_machines.rst:866
msgid "In the left navigation bar, click Templates."
msgstr ""
-#: ../../virtual_machines.rst:866
-# 0f973ef8ca224955a380e55e4cb178f7
+#: ../../virtual_machines.rst:868
msgid "In Select View, choose ISOs."
msgstr ""
-#: ../../virtual_machines.rst:868
-# 7fa77a1f7f2c433b9a91a2674c905e0f
+#: ../../virtual_machines.rst:870
msgid "Click Add ISO."
msgstr ""
-#: ../../virtual_machines.rst:870
-# d823b6abfa4f4f90a537b89a3028cbf8
+#: ../../virtual_machines.rst:872
msgid "In the Add ISO screen, provide the following:"
msgstr ""
-#: ../../virtual_machines.rst:872
-# 3685d0bb311b4ed380fda725b7cd9278
+#: ../../virtual_machines.rst:874
msgid "**Name**: Short name for the ISO image. For example, CentOS 6.2 64-bit."
msgstr ""
-#: ../../virtual_machines.rst:875
-# 2b4eed14408848cdba835ad59d43680e
+#: ../../virtual_machines.rst:877
msgid "**Description**: Display test for the ISO image. For example, CentOS
6.2 64-bit."
msgstr ""
-#: ../../virtual_machines.rst:878
-# f186dace19cc4fb78d4e957564d8542e
+#: ../../virtual_machines.rst:880
msgid "**URL**: The URL that hosts the ISO image. The Management Server must
be able to access this location via HTTP. If needed you can place the ISO image
directly on the Management Server"
msgstr ""
-#: ../../virtual_machines.rst:882
-# 425e7404b8194bb5931d02792793408e
+#: ../../virtual_machines.rst:884
msgid "**Zone**: Choose the zone where you want the ISO to be available, or
All Zones to make it available throughout CloudStack."
msgstr ""
-#: ../../virtual_machines.rst:885
-# aa204bdaf6d9433bb4412c757dc5d44b
+#: ../../virtual_machines.rst:887
msgid "**Bootable**: Whether or not a guest could boot off this ISO image. For
example, a CentOS ISO is bootable, a Microsoft Office ISO is not bootable."
msgstr ""
-#: ../../virtual_machines.rst:889
-# 8b59d99740ca42ecbb70e61c148a6cea
+#: ../../virtual_machines.rst:891
msgid "**OS Type**: This helps CloudStack and the hypervisor perform certain
operations and make assumptions that improve the performance of the guest.
Select one of the following."
msgstr ""
-#: ../../virtual_machines.rst:893
-# 55d339b4332b4f8d90ab0c41ac4064b8
+#: ../../virtual_machines.rst:895
msgid "If the operating system of your desired ISO image is listed, choose it."
msgstr ""
-#: ../../virtual_machines.rst:896
-# 7181c3bfc6ea45d29f5de6686bdbc0c8
+#: ../../virtual_machines.rst:898
msgid "If the OS Type of the ISO is not listed or if the ISO is not bootable,
choose Other."
msgstr ""
-#: ../../virtual_machines.rst:899
-# 121ed273b9d942f0bcab107605fbc155
+#: ../../virtual_machines.rst:901
msgid "(XenServer only) If you want to boot from this ISO in PV mode, choose
Other PV (32-bit) or Other PV (64-bit)"
msgstr ""
-#: ../../virtual_machines.rst:902
-# 4630b5213f5447b692ec7949d9d2d0b8
+#: ../../virtual_machines.rst:904
msgid "(KVM only) If you choose an OS that is PV-enabled, the VMs created from
this ISO will have a SCSI (virtio) root disk. If the OS is not PV-enabled, the
VMs will have an IDE root disk. The PV-enabled types are:"
msgstr ""
-#: ../../virtual_machines.rst:907
-# 635be29dfcf3483a8f0a22d1a6baccd9
+#: ../../virtual_machines.rst:909
msgid "Fedora 13"
msgstr ""
-#: ../../virtual_machines.rst:909
-# 93e9c1d5a6a3487d8c2c3fa739eaf98d
+#: ../../virtual_machines.rst:911
msgid "Fedora 12"
msgstr ""
-#: ../../virtual_machines.rst:911
-# 2a8eeb99d2ea4a3bac651072df26da55
+#: ../../virtual_machines.rst:913
msgid "Fedora 11"
msgstr ""
-#: ../../virtual_machines.rst:913
-# c31cbc941bb44094846e2e60cddb38b8
+#: ../../virtual_machines.rst:915
msgid "Fedora 10"
msgstr ""
-#: ../../virtual_machines.rst:915
-# 46d96452f5e645899cdbeed2f1d8dd64
+#: ../../virtual_machines.rst:917
msgid "Fedora 9"
msgstr ""
-#: ../../virtual_machines.rst:917
-# 4b44f056e016456b86e5d94d780f5c70
+#: ../../virtual_machines.rst:919
msgid "Other PV"
msgstr ""
-#: ../../virtual_machines.rst:919
-# 1f0bbb7dcde34e43a90ab458542c9245
+#: ../../virtual_machines.rst:921
msgid "Debian GNU/Linux"
msgstr ""
-#: ../../virtual_machines.rst:921
-# fa0ff295703648b6a27c3051e80cc1a7
+#: ../../virtual_machines.rst:923
msgid "CentOS 5.3"
msgstr ""
-#: ../../virtual_machines.rst:923
-# 10c5d0e4740249ef938a3af66c83cbd4
+#: ../../virtual_machines.rst:925
msgid "CentOS 5.4"
msgstr ""
-#: ../../virtual_machines.rst:925
-# 3abebb97eac94950b3928ed76316c4fb
+#: ../../virtual_machines.rst:927
msgid "CentOS 5.5"
msgstr ""
-#: ../../virtual_machines.rst:927
-# 6e43cd1649cc453eb9ddd4fd035c80cc
+#: ../../virtual_machines.rst:929
msgid "Red Hat Enterprise Linux 5.3"
msgstr ""
-#: ../../virtual_machines.rst:929
-# 460371604538459f9aaab9dbec447cdd
+#: ../../virtual_machines.rst:931
msgid "Red Hat Enterprise Linux 5.4"
msgstr ""
-#: ../../virtual_machines.rst:931
-# 7d68f48aeac44031b6cd313d5fc799a1
+#: ../../virtual_machines.rst:933
msgid "Red Hat Enterprise Linux 5.5"
msgstr ""
-#: ../../virtual_machines.rst:933
-# a2764fbb27c34b978dae6142215c6850
+#: ../../virtual_machines.rst:935
msgid "Red Hat Enterprise Linux 6"
msgstr ""
-#: ../../virtual_machines.rst:936
-# 94dfebd340a74c8b88a2994cc95f58ec
+#: ../../virtual_machines.rst:938
msgid "It is not recommended to 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 usually not work. In these cases, choose Other."
msgstr ""
-#: ../../virtual_machines.rst:941
-# f097cba5535645278ee6719b4a03072a
+#: ../../virtual_machines.rst:943
msgid "**Extractable**: Choose Yes if the ISO should be available for
extraction."
msgstr ""
-#: ../../virtual_machines.rst:944
-# 7d047a068b0a49599ef129b9c79a6666
+#: ../../virtual_machines.rst:946
msgid "**Public**: Choose Yes if this ISO should be available to other users."
msgstr ""
-#: ../../virtual_machines.rst:947
-# cc70871cc63f4a778f5a762c96814820
+#: ../../virtual_machines.rst:949
msgid "**Featured**: Choose Yes if you would like this ISO to be more
prominent for users to select. The ISO will appear in the Featured ISOs list.
Only an administrator can make an ISO Featured."
msgstr ""
-#: ../../virtual_machines.rst:953
-# 0ada7b2845314dff81bc2025971a349d
+#: ../../virtual_machines.rst:955
msgid "The Management Server will download the ISO. Depending on the size of
the ISO, this may take a long time. The ISO status column will display Ready
once it has been successfully downloaded into secondary storage. Clicking
Refresh updates the download percentage."
msgstr ""
-#: ../../virtual_machines.rst:958
-# 6918d4062b5b40fe9ec994fe73602e85
+#: ../../virtual_machines.rst:960
msgid "**Important**: Wait for the ISO to finish downloading. If you move on
to the next task and try to use the ISO right away, it will appear to fail. The
entire ISO must be available before CloudStack can work with it."
msgstr ""
-#: ../../virtual_machines.rst:965
-# b14f8c054f394494acb88245da8ba860
+#: ../../virtual_machines.rst:967
msgid "Attaching an ISO to a VM"
msgstr ""
-#: ../../virtual_machines.rst:969
-# b5dd3e88e7fd4e289eaba6d0a5144d12
+#: ../../virtual_machines.rst:971
msgid "Choose the virtual machine you want to work with."
msgstr ""
-#: ../../virtual_machines.rst:971
-# 7dc31f79f1d14b79a420d462bfee1c59
+#: ../../virtual_machines.rst:973
msgid "Click the Attach ISO button. |iso.png|"
msgstr ""
-#: ../../virtual_machines.rst:973
-# c8a3faf4703b4ccd9b1e8108195cc959
+#: ../../virtual_machines.rst:975
msgid "In the Attach ISO dialog box, select the desired ISO."
msgstr ""
-#: ../../virtual_machines.rst:979
-# 549b92307c7f47f98184d3f1124fa408
+#: ../../virtual_machines.rst:981
msgid "Changing a VM's Base Image"
msgstr ""
-#: ../../virtual_machines.rst:981
-# 13e3fdc48e0047a987a24ca40e0e1a87
+#: ../../virtual_machines.rst:983
msgid "Every VM is created from a base image, which is a template or ISO which
has been created and stored in CloudStack. Both cloud administrators and end
users can create and modify templates, ISOs, and VMs."
msgstr ""
-#: ../../virtual_machines.rst:985
-# f5fa30e2adb14813a20639e4efb5b685
+#: ../../virtual_machines.rst:987
msgid "In CloudStack, you can change an existing VM's base image from one
template to another, or from one ISO to another. (You can not change from an
ISO to a template, or from a template to an ISO)."
msgstr ""
-#: ../../virtual_machines.rst:989
-# 950431c149ec42938db84b6db95abf20
+#: ../../virtual_machines.rst:991
msgid "For example, suppose there is a template based on a particular
operating system, and the OS vendor releases a software patch. The
administrator or user naturally wants to apply the patch and then make sure
existing VMs start using it. Whether a software update is involved or not, it's
also possible to simply switch a VM from its current template to any other
desired template."
msgstr ""
-#: ../../virtual_machines.rst:996
-# fee5003ddd3f4dbbaba68ad0e14fe0d0
+#: ../../virtual_machines.rst:998
msgid "To change a VM's base image, call the restoreVirtualMachine API command
and pass in the virtual machine ID and a new template ID. The template ID
parameter may refer to either a template or an ISO, depending on which type of
base image the VM was already using (it must match the previous type of image).
When this call occurs, the VM's root disk is first destroyed, then a new root
disk is created from the source designated in the template ID parameter. The
new root disk is attached to the VM, and now the VM is based on the new
template."
msgstr ""
-#: ../../virtual_machines.rst:1005
-# 0b104b6b42e9463c92201dd3799d82d6
+#: ../../virtual_machines.rst:1007
msgid "You can also omit the template ID parameter from the
restoreVirtualMachine call. In this case, the VM's root disk is destroyed and
recreated, but from the same template or ISO that was already in use by the VM."
msgstr ""
-#: ../../virtual_machines.rst:1012
-# e0d3653b842a43b7bd3f9cba8bfb4397
+#: ../../virtual_machines.rst:1014
msgid "Using SSH Keys for Authentication"
msgstr ""
-#: ../../virtual_machines.rst:1014
-# f04e7ecfb1314f84ab38410cef835634
+#: ../../virtual_machines.rst:1016
msgid "In addition to the username and password authentication, CloudStack
supports using SSH keys to log in to the cloud infrastructure for additional
security. You can use the createSSHKeyPair API to generate the SSH keys."
msgstr ""
-#: ../../virtual_machines.rst:1019
-# 007515e3abea40618c568f35513e1571
+#: ../../virtual_machines.rst:1021
msgid "Because each cloud user has their own SSH key, one cloud user cannot
log in to another cloud user's instances unless they share their SSH key files.
Using a single SSH key pair, you can manage multiple instances."
msgstr ""
-#: ../../virtual_machines.rst:1025
-# 0edd947ce47c438daad162beb19d2fd7
+#: ../../virtual_machines.rst:1027
msgid "Creating an Instance Template that Supports SSH Keys"
msgstr ""
-#: ../../virtual_machines.rst:1027
-# f2ce122e2dcf433a8945e8c2d923e2b6
+#: ../../virtual_machines.rst:1029
msgid "Create an instance template that supports SSH Keys."
msgstr ""
-#: ../../virtual_machines.rst:1029
-# c683112d085244fabffdc696c868fdf2
+#: ../../virtual_machines.rst:1031
msgid "Create a new instance by using the template provided by cloudstack."
msgstr ""
-#: ../../virtual_machines.rst:1031
-# 0409d2f2d7964ac28bfeb8bed3f58e12
+#: ../../virtual_machines.rst:1033
msgid "For more information on creating a new instance, see"
msgstr ""
-#: ../../virtual_machines.rst:1033
-# 497da833fd9642c39f7ca84fadb0ce84
+#: ../../virtual_machines.rst:1035
msgid "Download the cloudstack script from `The SSH Key Gen Script
<http://sourceforge.net/projects/cloudstack/files/SSH%20Key%20Gen%20Script/>`_
to the instance you have created."
msgstr ""
-#: ../../virtual_machines.rst:1041
-# 339a3d87be144308915639d37c89ea1d
+#: ../../virtual_machines.rst:1043
msgid "Copy the file to /etc/init.d."
msgstr ""
-#: ../../virtual_machines.rst:1047
-# f601fce5097849559dc10a71eeb440a9
+#: ../../virtual_machines.rst:1049
msgid "Give the necessary permissions on the script:"
msgstr ""
-#: ../../virtual_machines.rst:1053
-# a5a38d6cf81845aa81cbb049a6c03108
+#: ../../virtual_machines.rst:1055
msgid "Run the script while starting up the operating system:"
msgstr ""
-#: ../../virtual_machines.rst:1059
-# 733b18c1fccb453396b69626f1da7452
+#: ../../virtual_machines.rst:1061
msgid "Stop the instance."
msgstr ""
-#: ../../virtual_machines.rst:1063
-# 580da0c9298f41699deb34011b0310e6
+#: ../../virtual_machines.rst:1065
msgid "Creating the SSH Keypair"
msgstr ""
-#: ../../virtual_machines.rst:1065
-# c5ac52360d7941528588398acbb420e8
+#: ../../virtual_machines.rst:1067
msgid "You must make a call to the createSSHKeyPair api method. You can either
use the CloudStack Python API library or the curl commands to make the call to
the cloudstack api."
msgstr ""
-#: ../../virtual_machines.rst:1069
-# 89cec2df86664c26bafeddd6fd2aa054
+#: ../../virtual_machines.rst:1071
msgid "For example, make a call from the cloudstack server to create a SSH
keypair called \"keypair-doc\" for the admin account in the root domain:"
msgstr ""
-#: ../../virtual_machines.rst:1073
-# c57fbd36512446559d91c1b7eeff7cea
+#: ../../virtual_machines.rst:1075
msgid "Ensure that you adjust these values to meet your needs. If you are
making the API call from a different server, your URL/PORT will be different,
and you will need to use the API keys."
msgstr ""
-#: ../../virtual_machines.rst:1077
-# 6d651f1b57ef4e81ade3cdafcc642e4b
+#: ../../virtual_machines.rst:1079
msgid "Run the following curl command:"
msgstr ""
-#: ../../virtual_machines.rst:1083
-# 665246c92ab74234b1790979863082a7
+#: ../../virtual_machines.rst:1085
msgid "The output is something similar to what is given below:"
msgstr ""
-#: ../../virtual_machines.rst:1101
-# 64c5993f04f043b5a0e5925aef2db171
+#: ../../virtual_machines.rst:1103
msgid "Copy the key data into a file. The file looks like this:"
msgstr ""
-#: ../../virtual_machines.rst:1118
-# cf75a310b6854564b8053aa63328f6ce
+#: ../../virtual_machines.rst:1120
msgid "Save the file."
msgstr ""
-#: ../../virtual_machines.rst:1122
-# 87cc3ec398db47f09bc21e1a66c8720f
+#: ../../virtual_machines.rst:1124
msgid "Creating an Instance"
msgstr ""
-#: ../../virtual_machines.rst:1124
-# e115c665e72345fcab3fc94458caa818
+#: ../../virtual_machines.rst:1126
msgid "After you save the SSH keypair file, you must create an instance by
using the template that you created at `Section 5.2.1, â Creating an
Instance Template that Supports SSH Keysâ <#create-ssh-template>`__. Ensure
that you use the same SSH key name that you created at `Section 5.2.2,
âCreating the SSH Keypairâ <#create-ssh-keypair>`__."
msgstr ""
-#: ../../virtual_machines.rst:1131
-# 8e5a7943aaf741989b2f9aa7c92fa061
+#: ../../virtual_machines.rst:1133
msgid "You cannot create the instance by using the GUI at this time and
associate the instance with the newly created SSH keypair."
msgstr ""
-#: ../../virtual_machines.rst:1134
-# bb36e5f1a5cc497bb95f96481cd3c232
+#: ../../virtual_machines.rst:1136
msgid "A sample curl command to create a new instance is:"
msgstr ""
-#: ../../virtual_machines.rst:1140
-# 9a98f03016ba40f1b8eb932e8e15a75c
+#: ../../virtual_machines.rst:1142
msgid "Substitute the template, service offering and security group IDs (if
you are using the security group feature) that are in your cloud environment."
msgstr ""
-#: ../../virtual_machines.rst:1146
-# 9c448726db0b469bb32323df48aeba12
+#: ../../virtual_machines.rst:1148
msgid "Logging In Using the SSH Keypair"
msgstr ""
-#: ../../virtual_machines.rst:1148
-# 5276ff9c384b4372bc6814b7f7461ae2
+#: ../../virtual_machines.rst:1150
msgid "To test your SSH key generation is successful, check whether you can
log in to the cloud setup."
msgstr ""
-#: ../../virtual_machines.rst:1151
-# 632b48d2ebaf4620be47c9bc1b6e1d39
+#: ../../virtual_machines.rst:1153
msgid "For example, from a Linux OS, run:"
msgstr ""
-#: ../../virtual_machines.rst:1157
-# b597ba33b4154d5c95931e7a30a1aa41
+#: ../../virtual_machines.rst:1159
msgid "The -i parameter tells the ssh client to use a ssh key found at
~/.ssh/keypair-doc."
msgstr ""
-#: ../../virtual_machines.rst:1162
-# 0ebe651140d94e709efff80066e042b7
+#: ../../virtual_machines.rst:1164
msgid "Resetting SSH Keys"
msgstr ""
-#: ../../virtual_machines.rst:1164
-# 1367090489eb4ad68179bce4ba266e37
+#: ../../virtual_machines.rst:1166
msgid "With the API command resetSSHKeyForVirtualMachine, a user can set or
reset the SSH keypair assigned to a virtual machine. A lost or compromised SSH
keypair can be changed, and the user can access the VM by using the new
keypair. Just create or register a new keypair, then call
resetSSHKeyForVirtualMachine."
msgstr ""
+#: ../../virtual_machines/user-data.rst:18
+msgid "User-Data and Meta-Data"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:20
+msgid "CloudStack provides API access to attach up to 2KB of data after base64
encoding to a deployed VM. Using HTTP POST(via POST body), you can send up to
32K of data after base64 encoding. Deployed VMs also have access to instance
metadata via the virtual router."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:25
+msgid "Create virtual machine thru the API: `deployVirtualMachine
<http://cloudstack.apache.org/docs/api/apidocs-4.5/user/deployVirtualMachine.html>`_
using the parameter ``userdata=`` to include user-data formated in `base64
<https://www.base64encode.org/>`_."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:29
+msgid "Accessed user-data from VM. Once the IP address of the virtual router
is known, use the following steps to retrieve user-data:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:32
+msgid "Run the following command to find the virtual router."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:38
+msgid "Access user-data by running the following command using the result of
the above command"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:45
+msgid "Meta Data can be accessed similarly, using a URL of the form
``http://10.1.1.1/latest/meta-data/{metadata type}``. (For backwards
compatibility, the previous URL ``http://10.1.1.1/latest/{metadata type}`` is
also supported.) For metadata type, use one of the following:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:50
+msgid "``service-offering``. A description of the VMs service offering"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:52
+msgid "``availability-zone``. The Zone name"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:54
+msgid "``local-ipv4``. The guest IP of the VM"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:56
+msgid "``local-hostname``. The hostname of the VM"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:58
+msgid "``public-ipv4``. The first public IP for the router. (E.g. the first IP
of eth2)"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:61
+msgid "``public-hostname``. This is the same as public-ipv4"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:63
+msgid "``instance-id``. The instance name of the VM"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:67
+msgid "Using Cloud-Init"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:69
+msgid "`Cloud-Init <https://cloudinit.readthedocs.org/en/latest>`_ can be use
to access an interpret user-data from virtual machines. Cloud-Init be installed
into templates and also require CloudStack password and sshkey scripts
(:ref:`adding-password-management-to-templates` and `using ssh keys
<virtual_machines.html#using-ssh-keys-for-authentication>`_). User password
management and ``resetSSHKeyForVirtualMachine`` API are not yet supported by
cloud-init."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:74
+msgid "Install cloud-init package into a template:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:82
+msgid "Create datasource configuration file:
``/etc/cloud/cloud.cfg.d/99_cloudstack.cfg``"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:94
+msgid "user-data example"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:96
+msgid "This example use cloud-init to Upgrade Operating-System of the newly
created VM:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:110
+msgid "base64 formated:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:116
+msgid "Refer to `Cloud-Init CloudStack datasource
<http://cloudinit.readthedocs.org/en/latest/topics/datasources.html#cloudstack>`_
documentation for latest capabilities. Cloud-Init and Cloud-Init CloudStack
datasource are not supported by Apache CloudStack community."
+msgstr ""
+
+#: ../../virtual_machines.rst:1176
+msgid "Assigning GPU/vGPU to Guest VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:1178
+msgid "CloudStack can deploy guest VMs with Graphics Processing Unit (GPU) or
Virtual Graphics Processing Unit (vGPU) capabilities on XenServer hosts. At the
time of VM deployment or at a later stage, you can assign a physical GPU (
known as GPU-passthrough) or a portion of a physical GPU card (vGPU) to a guest
VM by changing the Service Offering. With this capability, the VMs running on
CloudStack meet the intensive graphical processing requirement by means of the
high computation power of GPU/vGPU, and CloudStack users can run multimedia
rich applications, such as Auto-CAD, that they otherwise enjoy at their desk on
a virtualized environment. CloudStack leverages the XenServer support for
NVIDIA GRID Kepler 1 and 2 series to run GPU/vGPU enabled VMs. NVIDIA GRID
cards allows sharing a single GPU cards among multiple VMs by creating vGPUs
for each VM. With vGPU technology, the graphics commands from each VM are
passed directly to the underlying dedicated GPU, without the interventi
on of the hypervisor. This allows the GPU hardware to be time-sliced and
shared across multiple VMs. XenServer hosts use the GPU cards in following
ways:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1195
+msgid "**GPU passthrough**: GPU passthrough represents a physical GPU which
can be directly assigned to a VM. GPU passthrough can be used on a hypervisor
alongside GRID vGPU, with some restrictions: A GRID physical GPU can either
host GRID vGPUs or be used as passthrough, but not both at the same time."
+msgstr ""
+
+#: ../../virtual_machines.rst:1200
+msgid "**GRID vGPU**: GRID vGPU enables multiple VMs to share a single
physical GPU. The VMs run an NVIDIA driver stack and get direct access to the
GPU. GRID physical GPUs are capable of supporting multiple virtual GPU devices
(vGPUs) that can be assigned directly to guest VMs. Guest VMs use GRID virtual
GPUs in the same manner as a physical GPU that has been passed through by the
hypervisor: an NVIDIA driver loaded in the guest VM provides direct access to
the GPU for performance-critical fast paths, and a paravirtualized interface to
the GRID Virtual GPU Manager, which is used for nonperformant management
operations. NVIDIA GRID Virtual GPU Manager for XenServer runs in dom0.
CloudStack provides you with the following capabilities:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1211
+msgid "Adding XenServer hosts with GPU/vGPU capability provisioned by the
administrator."
+msgstr ""
+
+#: ../../virtual_machines.rst:1213
+msgid "Creating a Compute Offering with GPU/vGPU capability."
+msgstr ""
+
+#: ../../virtual_machines.rst:1215
+msgid "Deploying a VM with GPU/vGPU capability."
+msgstr ""
+
+#: ../../virtual_machines.rst:1217
+msgid "Destroying a VM with GPU/vGPU capability."
+msgstr ""
+
+#: ../../virtual_machines.rst:1219
+msgid "Allowing an user to add GPU/vGPU support to a VM without GPU/vGPU
support by changing the Service Offering and vice-versa."
+msgstr ""
+
+#: ../../virtual_machines.rst:1222
+msgid "Migrating VMs (cold migration) with GPU/vGPU capability."
+msgstr ""
+
+#: ../../virtual_machines.rst:1224
+msgid "Managing GPU cards capacity."
+msgstr ""
+
+#: ../../virtual_machines.rst:1226
+msgid "Querying hosts to obtain information about the GPU cards, supported
vGPU types in case of GRID cards, and capacity of the cards."
+msgstr ""
+
+#: ../../virtual_machines.rst:1230
+msgid "Prerequisites and System Requirements"
+msgstr ""
+
+#: ../../virtual_machines.rst:1232
+msgid "Before proceeding, ensure that you have these prerequisites:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1234
+msgid "The vGPU-enabled XenServer 6.2 and later versions. For more
information, see `Citrix 3D Graphics Pack
<https://www.citrix.com/go/private/vgpu.html>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:1237
+msgid "GPU/vPGU functionality is supported for following HVM guest operating
systems: For more information, see `Citrix 3D Graphics Pack
<https://www.citrix.com/go/private/vgpu.html>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:1240
+msgid "Windows 7 (x86 and x64)"
+msgstr ""
+
+#: ../../virtual_machines.rst:1242
+msgid "Windows Server 2008 R2"
+msgstr ""
+
+#: ../../virtual_machines.rst:1244
+msgid "Windows Server 2012"
+msgstr ""
+
+#: ../../virtual_machines.rst:1246
+msgid "Windows 8 (x86 and x64)"
+msgstr ""
+
+#: ../../virtual_machines.rst:1248
+msgid "Windows 8.1 (\"Blue\") (x86 and x64)"
+msgstr ""
+
+#: ../../virtual_machines.rst:1250
+msgid "Windows Server 2012 R2 (server equivalent of \"Blue\")"
+msgstr ""
+
+#: ../../virtual_machines.rst:1252
+msgid "CloudStack does not restrict the deployment of GPU-enabled VMs with
guest OS types that are not supported by XenServer for GPU/vGPU functionality.
The deployment would be successful and a GPU/vGPU will also get allocated for
VMs; however, due to missing guest OS drivers, VM would not be able to leverage
GPU resources. Therefore, it is recommended to use GPU-enabled service offering
only with supported guest OS."
+msgstr ""
+
+#: ../../virtual_machines.rst:1254
+msgid "NVIDIA GRID K1 (16 GiB video RAM) AND K2 (8 GiB of video RAM) cards
supports homogeneous virtual GPUs, implies that at any given time, the vGPUs
resident on a single physical GPU must be all of the same type. However, this
restriction doesn't extend across physical GPUs on the same card. Each physical
GPU on a K1 or K2 may host different types of virtual GPU at the same time. For
example, a GRID K2 card has two physical GPUs, and supports four types of
virtual GPU; GRID K200, GRID K220Q, GRID K240Q, AND GRID K260Q."
+msgstr ""
+
+#: ../../virtual_machines.rst:1256
+msgid "NVIDIA driver must be installed to enable vGPU operation as for a
physical NVIDIA GPU."
+msgstr ""
+
+#: ../../virtual_machines.rst:1258
+msgid "XenServer tools are installed in the VM to get maximum performance on
XenServer, regardless of type of vGPU you are using. Without the optimized
networking and storage drivers that the XenServer tools provide, remote
graphics applications running on GRID vGPU will not deliver maximum
performance."
+msgstr ""
+
+#: ../../virtual_machines.rst:1260
+msgid "To deliver high frames from multiple heads on vGPU, install XenDesktop
with HDX 3D Pro remote graphics."
+msgstr ""
+
+#: ../../virtual_machines.rst:1262
+msgid "Before continuing with configuration, consider the following:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1264
+msgid "Deploying VMs GPU/vGPU capability is not supported if hosts are not
available with enough GPU capacity."
+msgstr ""
+
+#: ../../virtual_machines.rst:1266
+msgid "A Service Offering cannot be created with the GPU values that are not
supported by CloudStack UI. However, you can make an API call to achieve this."
+msgstr ""
+
+#: ../../virtual_machines.rst:1268
+msgid "Dynamic scaling is not supported. However, you can choose to deploy a
VM without GPU support, and at a later point, you can change the system
offering to upgrade to the one with vGPU. You can achieve this by offline
upgrade: stop the VM, upgrade the Service Offering to the one with vGPU, then
start the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:1270
+msgid "Live migration of GPU/vGPU enabled VM is not supported."
+msgstr ""
+
+#: ../../virtual_machines.rst:1272
+msgid "Limiting GPU resources per Account/Domain is not supported."
+msgstr ""
+
+#: ../../virtual_machines.rst:1274
+msgid "Disabling GPU at Cluster level is not supported."
+msgstr ""
+
+#: ../../virtual_machines.rst:1276
+msgid "Notification thresholds for GPU resource is not supported."
+msgstr ""
+
+#: ../../virtual_machines.rst:1279
+msgid "Supported GPU Devices"
+msgstr ""
+
+#: ../../virtual_machines.rst:1284
+msgid "Device"
+msgstr ""
+
+#: ../../virtual_machines.rst:1284
+msgid "Type"
+msgstr ""
+
+#: ../../virtual_machines.rst:1286
+msgid "GPU"
+msgstr ""
+
+#: ../../virtual_machines.rst:1286
+msgid "Group of NVIDIA Corporation GK107GL [GRID K1] GPUs"
+msgstr ""
+
+#: ../../virtual_machines.rst:1287
+msgid "Group of NVIDIA Corporation GK104GL [GRID K2] GPUs"
+msgstr ""
+
+#: ../../virtual_machines.rst:1288
+msgid "Any other GPU Group"
+msgstr ""
+
+#: ../../virtual_machines.rst:1289
+msgid "vGPU"
+msgstr ""
+
+#: ../../virtual_machines.rst:1289
+msgid "GRID K100"
+msgstr ""
+
+#: ../../virtual_machines.rst:1290
+msgid "GRID K120Q"
+msgstr ""
+
+#: ../../virtual_machines.rst:1291
+msgid "GRID K140Q"
+msgstr ""
+
+#: ../../virtual_machines.rst:1292
+msgid "GRID K200"
+msgstr ""
+
+#: ../../virtual_machines.rst:1293
+msgid "GRID K220Q"
+msgstr ""
+
+#: ../../virtual_machines.rst:1294
+msgid "GRID K240Q"
+msgstr ""
+
+#: ../../virtual_machines.rst:1295
+msgid "GRID K260Q"
+msgstr ""
+
+#: ../../virtual_machines.rst:1299
+msgid "GPU/vGPU Assignment Workflow"
+msgstr ""
+
+#: ../../virtual_machines.rst:1302
+msgid "CloudStack follows the below sequence of operations to provide GPU/vGPU
support for VMs:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1304
+msgid "Ensure that XenServer host is ready with GPU installed and configured.
For more information, see `Citrix 3D Graphics Pack
<https://www.citrix.com/go/private/vgpu.html>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:1307
+msgid "Add the host to CloudStack. CloudStack checks if the host is
GPU-enabled or not. CloudStack queries the host and detect if it's GPU enabled."
+msgstr ""
+
+#: ../../virtual_machines.rst:1310
+msgid "Create a compute offering with GPU/vGPU support: For more information,
see `Creating a New Compute Offering <#creating-a-new-compute-offering>`__.."
+msgstr ""
+
+#: ../../virtual_machines.rst:1313
+msgid "Continue with any of the following operations:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1315
+msgid "Deploy a VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:1317
+msgid "Deploy a VM with GPU/vGPU support by selecting appropriate Service
Offering. CloudStack decide which host to choose for VM deployment based on
following criteria:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1319
+msgid "Host has GPU cards in it. In case of vGPU, CloudStack checks if cards
have the required vGPU type support and enough capacity available. Having no
appropriate hosts results in an InsufficientServerCapacity exception."
+msgstr ""
+
+#: ../../virtual_machines.rst:1321
+msgid "Alternately, you can choose to deploy a VM without GPU support, and at
a later point, you can change the system offering. You can achieve this by
offline upgrade: stop the VM, upgrade the Service Offering to the one with
vGPU, then start the VM. In this case, CloudStack gets a list of hosts which
have enough capacity to host the VM. If there is a GPU-enabled host, CloudStack
reorders this host list and place the GPU-enabled hosts at the bottom of the
list."
+msgstr ""
+
+#: ../../virtual_machines.rst:1324
+msgid "Migrate a VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:1326
+msgid "CloudStack searches for hosts available for VM migration, which
satisfies GPU requirement. If the host is available, stop the VM in the
current host and perform the VM migration task. If the VM migration is
successful, the remaining GPU capacity is updated for both the hosts
accordingly."
+msgstr ""
+
+#: ../../virtual_machines.rst:1328
+msgid "Destroy a VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:1330
+msgid "GPU resources are released automatically when you stop a VM. Once the
destroy VM is successful, CloudStack will make a resource call to the host to
get the remaining GPU capacity in the card and update the database accordingly."
+msgstr ""
+
