mirror of
https://github.com/apache/cloudstack.git
synced 2025-10-26 08:42:29 +01:00
118 lines
5.5 KiB
XML
118 lines
5.5 KiB
XML
<?xml version='1.0' encoding='utf-8' ?>
|
|
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
|
|
%BOOK_ENTITIES;
|
|
]>
|
|
<!-- Licensed to the Apache Software Foundation (ASF) under one
|
|
or more contributor license agreements. See the NOTICE file
|
|
distributed with this work for additional information
|
|
regarding copyright ownership. The ASF licenses this file
|
|
to you under the Apache License, Version 2.0 (the
|
|
"License"); you may not use this file except in compliance
|
|
with the License. You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing,
|
|
software distributed under the License is distributed on an
|
|
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
KIND, either express or implied. See the License for the
|
|
specific language governing permissions and limitations
|
|
under the License.
|
|
-->
|
|
<section id="creating-vms">
|
|
<title>Creating VMs</title>
|
|
<para>Virtual machines are usually created from a template. Users can also create blank virtual
|
|
machines. A blank virtual machine is a virtual machine without an OS template. Users can attach
|
|
an ISO file and install the OS from the CD/DVD-ROM.</para>
|
|
<note>
|
|
<para>You can create a VM without starting it. You can determine whether the VM needs to be
|
|
started as part of the VM deployment. A request parameter, startVM, in the deployVm API
|
|
provides this feature. For more information, see the Developer's Guide</para>
|
|
</note>
|
|
<para/>
|
|
<section id="creating-vm-from-template">
|
|
<title>Creating a VM from a template</title>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Log in to the &PRODUCT; UI as an administrator or user.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>In the left navigation bar, click Instances.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Click Add Instance.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Select a zone.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Select a template, then follow the steps in the wizard. For more information about how
|
|
the templates came to be in this list, see <xref linkend="working-with-templates"/>.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Be sure that the hardware you have allows starting the selected service offering.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Click Submit and your VM will be created and started.</para>
|
|
<note>
|
|
<para>For security reasons, the internal name of the VM is visible only to the root
|
|
admin.</para>
|
|
</note>
|
|
</listitem>
|
|
</orderedlist>
|
|
</section>
|
|
<section id="creating-vm-from-iso">
|
|
<title>Creating a VM from an ISO</title>
|
|
<note>
|
|
<para>(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.</para>
|
|
</note>
|
|
<para/>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Log in to the &PRODUCT; UI as an administrator or user.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>In the left navigation bar, click Instances.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Click Add Instance.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Select a zone.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Select ISO Boot, and follow the steps in the wizard.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Click Submit and your VM will be created and started.</para>
|
|
</listitem>
|
|
<!-- <listitem><para>(Oracle VM only) After ISO installation, the installer reboots into the operating system. Due to a known issue in OVM, the reboot will place the VM in the Stopped state. In the &PRODUCT; UI, detach the ISO from the VM (so that the VM will not boot from the ISO again), then click the Start button to restart the VM.</para></listitem> -->
|
|
</orderedlist>
|
|
</section>
|
|
<section id="vmware-configure-linked-clones">
|
|
<!-- CS-17387 -->
|
|
<title>Configuring Usage of Linked Clones on VMware</title>
|
|
<para>(For ESX hypervisor in conjunction with vCenter)</para>
|
|
<para>VMs can be created as either linked clones or full clones on VMware.</para>
|
|
<para>For a full description of clone types, refer to VMware documentation. In summary: A
|
|
full clone is a copy of an existing virtual machine which, once created, does not depend
|
|
in any way on the original virtual machine. A linked clone is also a copy of an existing
|
|
virtual machine, but it has ongoing dependency on the original. A linked clone shares the
|
|
virtual disk of the original VM, and retains access to all files that were present at the
|
|
time the clone was created.</para>
|
|
<para>The use of these different clone types involves some side effects and tradeoffs, so it
|
|
is to the administrator's advantage to be able to choose which of the two types will be
|
|
used in a &PRODUCT; deployment.</para>
|
|
<para>A new global configuration setting has been added, vmware.create.full.clone. When the
|
|
administrator sets this to true, end users can create guest VMs only as full clones. The
|
|
default value is false. </para>
|
|
<para>It is not recommended to change the value of vmware.create.full.clone in a cloud with
|
|
running VMs. However, if the value is changed, existing VMs are not affected. Only VMs
|
|
created after the setting is put into effect are subject to the restriction.</para>
|
|
</section>
|
|
</section>
|