mirror of
https://github.com/apache/cloudstack.git
synced 2025-12-21 04:53:37 +01:00
22 lines
4.6 KiB
HTML
22 lines
4.6 KiB
HTML
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.1. About Working with Virtual Machines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="next" href="best-practices-vm.html" title="10.2. Best Practices for Virtual Machines" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="virtual-machines.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="best-practices-vm.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-working-with-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-working-with-vms">10.1. About Working with Virtual Machines</h2></div></div></div><div class="para">
|
||
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.
|
||
</div><div class="para">
|
||
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:
|
||
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
|
||
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.
|
||
</div></li><li class="listitem"><div class="para">
|
||
Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name.
|
||
</div></li><li class="listitem"><div class="para">
|
||
Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name
|
||
</div></li></ul></div><div class="para">
|
||
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
|
||
</div><div class="para">
|
||
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.
|
||
</div><div class="para">
|
||
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.
|
||
</div><div class="para">
|
||
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.
|
||
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="virtual-machines.html"><strong>Prev</strong>Chapter 10. Working With Virtual Machines</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="best-practices-vm.html"><strong>Next</strong>10.2. Best Practices for Virtual Machines</a></li></ul></body></html>
|