mirror of
https://github.com/apache/cloudstack.git
synced 2025-10-26 08:42:29 +01:00
CLOUDSTACK-3300: Adding patches from cloudstack-1313
This commit is contained in:
Radhika PC
Sebastien Goasguen
parent
0304034822
commit
b68cc3346a
@ -21,24 +21,41 @@
|
|||||||
specific language governing permissions and limitations
|
specific language governing permissions and limitations
|
||||||
under the License.
|
under the License.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<section id="attaching-volume">
|
<section id="attaching-volume">
|
||||||
<title>Attaching a Volume</title>
|
<title>Attaching a Volume</title>
|
||||||
<para>You can attach a volume to a guest VM to provide extra disk storage. Attach a volume when you first create a new volume, when you are moving an existing volume from one VM to another, or after you have migrated a volume from one storage pool to another.</para>
|
<para>You can attach a volume to a guest VM to provide extra disk storage. Attach a volume when
|
||||||
|
you first create a new volume, when you are moving an existing volume from one VM to another, or
|
||||||
|
after you have migrated a volume from one storage pool to another.</para>
|
||||||
<orderedlist>
|
<orderedlist>
|
||||||
<listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem>
|
<listitem>
|
||||||
<listitem><para>In the left navigation, click Storage.</para></listitem>
|
<para>Log in to the &PRODUCT; UI as a user or admin.</para>
|
||||||
<listitem><para>In Select View, choose Volumes.</para></listitem>
|
</listitem>
|
||||||
<listitem><para>4. Click the volume name in the Volumes list, then click the Attach Disk button<inlinemediaobject>
|
<listitem>
|
||||||
|
<para>In the left navigation, click Storage.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>In Select View, choose Volumes.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>4. Click the volume name in the Volumes list, then click the Attach Disk button<inlinemediaobject>
|
||||||
<imageobject>
|
<imageobject>
|
||||||
<imagedata fileref="./images/attach-disk-icon.png"/>
|
<imagedata fileref="./images/attach-disk-icon.png"/>
|
||||||
</imageobject>
|
</imageobject>
|
||||||
<textobject><phrase>AttachDiskButton.png: button to attach a volume</phrase></textobject>
|
<textobject>
|
||||||
|
<phrase>AttachDiskButton.png: button to attach a volume</phrase>
|
||||||
|
</textobject>
|
||||||
</inlinemediaobject>
|
</inlinemediaobject>
|
||||||
</para></listitem>
|
</para>
|
||||||
<listitem><para>In the Instance popup, choose the VM to which you want to attach the volume. You will only see instances to which you are allowed to attach volumes; for example, a user will see only instances created by that user, but the administrator will have more choices.</para>
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>In the Instance popup, choose the VM to which you want to attach the volume. You will
|
||||||
|
only see instances to which you are allowed to attach volumes; for example, a user will see
|
||||||
|
only instances created by that user, but the administrator will have more choices.</para>
|
||||||
<!-- <para>If the VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
|
<!-- <para>If the VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem><para>When the volume has been attached, you should be able to see it by clicking Instances, the instance name, and View Volumes.</para></listitem>
|
<listitem>
|
||||||
|
<para>When the volume has been attached, you should be able to see it by clicking Instances,
|
||||||
|
the instance name, and View Volumes.</para>
|
||||||
|
</listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
</section>
|
</section>
|
||||||
|
|||||||
@ -23,41 +23,62 @@
|
|||||||
-->
|
-->
|
||||||
<section id="creating-new-volumes">
|
<section id="creating-new-volumes">
|
||||||
<title>Creating a New Volume</title>
|
<title>Creating a New Volume</title>
|
||||||
<para>You can add more data disk volumes to a guest VM at any time, up to the limits of your storage capacity. Both &PRODUCT; administrators and users can add volumes to VM instances. When you create a new volume, it is stored as an entity in &PRODUCT;, but the actual storage resources are not allocated on the physical storage device until you attach the volume. This optimization allows the &PRODUCT; to provision the volume nearest to the guest that will use it when the first attachment is made.</para>
|
<para>You can add more data disk volumes to a guest VM at any time, up to the limits of your
|
||||||
|
storage capacity. Both &PRODUCT; administrators and users can add volumes to VM instances. When
|
||||||
|
you create a new volume, it is stored as an entity in &PRODUCT;, but the actual storage
|
||||||
|
resources are not allocated on the physical storage device until you attach the volume. This
|
||||||
|
optimization allows the &PRODUCT; to provision the volume nearest to the guest that will use it
|
||||||
|
when the first attachment is made.</para>
|
||||||
<section id="local-storage-data-volumes">
|
<section id="local-storage-data-volumes">
|
||||||
<title>Using Local Storage for Data Volumes</title>
|
<title>Using Local Storage for Data Volumes</title>
|
||||||
<para>You can create data volumes on local storage (supported with XenServer, KVM, and VMware).
|
<para>You can create data volumes on local storage (supported with XenServer, KVM, and VMware).
|
||||||
The data volume is placed on the same
|
The data volume is placed on the same host as the VM instance that is attached to the data
|
||||||
host as the VM instance that is attached to the data volume. These
|
volume. These local data volumes can be attached to virtual machines, detached, re-attached,
|
||||||
local data volumes can be attached to virtual machines, detached, re-attached,
|
|
||||||
and deleted just as with the other types of data volume.</para>
|
and deleted just as with the other types of data volume.</para>
|
||||||
<para>Local storage is ideal for scenarios where persistence of data volumes and HA
|
<para>Local storage is ideal for scenarios where persistence of data volumes and HA is not
|
||||||
is not required. Some of the benefits include reduced disk I/O latency and cost
|
required. Some of the benefits include reduced disk I/O latency and cost reduction from using
|
||||||
reduction from using inexpensive local disks.</para>
|
inexpensive local disks.</para>
|
||||||
<para>In order for local volumes to be used, the feature must be enabled for the
|
<para>In order for local volumes to be used, the feature must be enabled for the zone.</para>
|
||||||
zone.</para>
|
<para>You can create a data disk offering for local storage. When a user creates a new VM, they
|
||||||
<para>You can create a data disk offering for local storage. When a user creates a
|
can select this disk offering in order to cause the data disk volume to be placed in local
|
||||||
new VM, they can select this disk offering in order to cause the data disk
|
storage.</para>
|
||||||
volume to be placed in local storage.</para>
|
<para>You can not migrate a VM that has a volume in local storage to a different host, nor
|
||||||
<para>You can not migrate a VM that has a volume in local storage to a different
|
migrate the volume itself away to a different host. If you want to put a host into maintenance
|
||||||
host, nor migrate the volume itself away to a different host. If you want to put
|
mode, you must first stop any VMs with local data volumes on that host.</para>
|
||||||
a host into maintenance mode, you must first stop any VMs with local data
|
|
||||||
volumes on that host.</para>
|
|
||||||
</section>
|
</section>
|
||||||
<section id="creating-new-volume-steps">
|
<section id="creating-new-volume-steps">
|
||||||
<title>To Create a New Volume</title>
|
<title>To Create a New Volume</title>
|
||||||
<orderedlist>
|
<orderedlist>
|
||||||
<listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem>
|
<listitem>
|
||||||
<listitem><para>In the left navigation bar, click Storage.</para></listitem>
|
<para>Log in to the &PRODUCT; UI as a user or admin.</para>
|
||||||
<listitem><para>In Select View, choose Volumes.</para></listitem>
|
</listitem>
|
||||||
<listitem><para>To create a new volume, click Add Volume, provide the following details, and click OK.</para>
|
<listitem>
|
||||||
|
<para>In the left navigation bar, click Storage.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>In Select View, choose Volumes.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>To create a new volume, click Add Volume, provide the following details, and click
|
||||||
|
OK.</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>Name. Give the volume a unique name so you can find it later.</para></listitem>
|
<listitem>
|
||||||
<listitem><para>Availability Zone. Where do you want the storage to reside? This should be close to the VM that will use the volume.</para></listitem>
|
<para>Name. Give the volume a unique name so you can find it later.</para>
|
||||||
<listitem><para>Disk Offering. Choose the characteristics of the storage.</para></listitem>
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Availability Zone. Where do you want the storage to reside? This should be close
|
||||||
|
to the VM that will use the volume.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Disk Offering. Choose the characteristics of the storage.</para>
|
||||||
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
<para>The new volume appears in the list of volumes with the state “Allocated.” The volume data is stored in &PRODUCT;, but the volume is not yet ready for use</para></listitem>
|
<para>The new volume appears in the list of volumes with the state “Allocated.” The volume
|
||||||
<listitem><para>To start using the volume, continue to Attaching a Volume </para></listitem>
|
data is stored in &PRODUCT;, but the volume is not yet ready for use</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>To start using the volume, continue to Attaching a Volume </para>
|
||||||
|
</listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|||||||
@ -23,14 +23,26 @@
|
|||||||
-->
|
-->
|
||||||
<section id="detach-move-volumes">
|
<section id="detach-move-volumes">
|
||||||
<title>Detaching and Moving Volumes</title>
|
<title>Detaching and Moving Volumes</title>
|
||||||
<note><para>This procedure is different from moving disk volumes from one storage pool to another. See VM Storage Migration </para></note>
|
<note>
|
||||||
<para>A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT; administrators and users can detach volumes from VMs and move them to other VMs.</para>
|
<para>This procedure is different from moving disk volumes from one storage pool to another. See
|
||||||
<para>If the two VMs are in different clusters, and the volume is large, it may take several minutes for the volume to be moved to the new VM.</para>
|
VM Storage Migration </para>
|
||||||
|
</note>
|
||||||
|
<para>A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT;
|
||||||
|
administrators and users can detach volumes from VMs and move them to other VMs.</para>
|
||||||
|
<para>If the two VMs are in different clusters, and the volume is large, it may take several
|
||||||
|
minutes for the volume to be moved to the new VM.</para>
|
||||||
<!-- <para>If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
|
<!-- <para>If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
|
||||||
<orderedlist>
|
<orderedlist>
|
||||||
<listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem>
|
<listitem>
|
||||||
<listitem><para>In the left navigation bar, click Storage, and choose Volumes in Select View. Alternatively, if you know which VM the volume is attached to, you can click Instances, click the VM name, and click View Volumes.</para></listitem>
|
<para>Log in to the &PRODUCT; UI as a user or admin.</para>
|
||||||
<listitem><para>Click the name of the volume you want to detach, then click the Detach Disk button. <inlinemediaobject>
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>In the left navigation bar, click Storage, and choose Volumes in Select View.
|
||||||
|
Alternatively, if you know which VM the volume is attached to, you can click Instances,
|
||||||
|
click the VM name, and click View Volumes.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Click the name of the volume you want to detach, then click the Detach Disk button. <inlinemediaobject>
|
||||||
<imageobject>
|
<imageobject>
|
||||||
<imagedata fileref="./images/detach-disk-icon.png"/>
|
<imagedata fileref="./images/detach-disk-icon.png"/>
|
||||||
</imageobject>
|
</imageobject>
|
||||||
@ -38,9 +50,11 @@
|
|||||||
<phrase>DetachDiskButton.png: button to detach a volume</phrase>
|
<phrase>DetachDiskButton.png: button to detach a volume</phrase>
|
||||||
</textobject>
|
</textobject>
|
||||||
</inlinemediaobject>
|
</inlinemediaobject>
|
||||||
</para></listitem>
|
</para>
|
||||||
<listitem><para>To move the volume to another VM, follow the steps in <xref linkend="attaching-volume"
|
</listitem>
|
||||||
/>.</para></listitem>
|
<listitem>
|
||||||
|
<para>To move the volume to another VM, follow the steps in <xref linkend="attaching-volume"
|
||||||
|
/>.</para>
|
||||||
|
</listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|||||||
@ -1,5 +1,5 @@
|
|||||||
<?xml version='1.0' encoding='utf-8' ?>
|
<?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" [
|
<!DOCTYPE chapter 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">
|
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
|
||||||
%BOOK_ENTITIES;
|
%BOOK_ENTITIES;
|
||||||
]>
|
]>
|
||||||
@ -21,7 +21,6 @@
|
|||||||
specific language governing permissions and limitations
|
specific language governing permissions and limitations
|
||||||
under the License.
|
under the License.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<chapter id="storage">
|
<chapter id="storage">
|
||||||
<title>Working With Storage</title>
|
<title>Working With Storage</title>
|
||||||
<xi:include href="storage-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
<xi:include href="storage-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
|
|||||||
@ -21,8 +21,8 @@
|
|||||||
specific language governing permissions and limitations
|
specific language governing permissions and limitations
|
||||||
under the License.
|
under the License.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<section id="upload-existing-volume-to-vm">
|
<section id="upload-existing-volume-to-vm">
|
||||||
|
<<<<<<< HEAD
|
||||||
<title>Uploading an Existing Volume to a Virtual Machine</title>
|
<title>Uploading an Existing Volume to a Virtual Machine</title>
|
||||||
<para>Existing data can be made accessible to a virtual machine. This is called uploading a volume to the VM. For example, this is useful to upload data from a local file system and attach it to a VM. Root administrators, domain administrators, and end users can all upload existing volumes to VMs.</para>
|
<para>Existing data can be made accessible to a virtual machine. This is called uploading a volume to the VM. For example, this is useful to upload data from a local file system and attach it to a VM. Root administrators, domain administrators, and end users can all upload existing volumes to VMs.</para>
|
||||||
<para>The upload is performed using HTTP. The uploaded volume is placed in the zone's secondary storage</para>
|
<para>The upload is performed using HTTP. The uploaded volume is placed in the zone's secondary storage</para>
|
||||||
@ -73,4 +73,92 @@
|
|||||||
</listitem>
|
</listitem>
|
||||||
<listitem><para>Wait until the status of the volume shows that the upload is complete. Click Instances - Volumes, find the name you specified in step <xref linkend="optional-hash"/>, and make sure the status is Uploaded.</para></listitem>
|
<listitem><para>Wait until the status of the volume shows that the upload is complete. Click Instances - Volumes, find the name you specified in step <xref linkend="optional-hash"/>, and make sure the status is Uploaded.</para></listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
|
=======
|
||||||
|
<title>Uploading an Existing Volume to a Virtual Machine</title>
|
||||||
|
<para>Existing data can be made accessible to a virtual machine. This is called uploading a volume
|
||||||
|
to the VM. For example, this is useful to upload data from a local file system and attach it to
|
||||||
|
a VM. Root administrators, domain administrators, and end users can all upload existing volumes
|
||||||
|
to VMs.</para>
|
||||||
|
<para>The upload is performed using HTTP. The uploaded volume is placed in the zone's secondary
|
||||||
|
storage</para>
|
||||||
|
<para>You cannot upload a volume if the preconfigured volume limit has already been reached. The
|
||||||
|
default limit for the cloud is set in the global configuration parameter max.account.volumes,
|
||||||
|
but administrators can also set per-domain limits that are different from the global default.
|
||||||
|
See Setting Usage Limits </para>
|
||||||
|
<para>To upload a volume:</para>
|
||||||
|
<orderedlist>
|
||||||
|
<listitem>
|
||||||
|
<para>(Optional) Create an MD5 hash (checksum) of the disk image file that you are going to
|
||||||
|
upload. After uploading the data disk, &PRODUCT; will use this value to verify that no data
|
||||||
|
corruption has occurred.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Log in to the &PRODUCT; UI as an administrator or user</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>In the left navigation bar, click Storage.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Click Upload Volume.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Provide the following:</para>
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem>
|
||||||
|
<para>Name and Description. Any desired name and a brief description that can be shown in
|
||||||
|
the UI.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Availability Zone. Choose the zone where you want to store the volume. VMs running
|
||||||
|
on hosts in this zone can attach the volume.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Format. Choose one of the following to indicate the disk image format of the
|
||||||
|
volume.</para>
|
||||||
|
<informaltable>
|
||||||
|
<tgroup cols="2" align="left" colsep="1" rowsep="1">
|
||||||
|
<thead>
|
||||||
|
<row>
|
||||||
|
<entry><para>Hypervisor</para></entry>
|
||||||
|
<entry><para>Disk Image Format</para></entry>
|
||||||
|
</row>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<row>
|
||||||
|
<entry><para>XenServer</para></entry>
|
||||||
|
<entry><para>VHD</para></entry>
|
||||||
|
</row>
|
||||||
|
<row>
|
||||||
|
<entry><para>VMware</para></entry>
|
||||||
|
<entry><para>OVA</para></entry>
|
||||||
|
</row>
|
||||||
|
<row>
|
||||||
|
<entry><para>KVM</para></entry>
|
||||||
|
<entry><para>QCOW2</para></entry>
|
||||||
|
</row>
|
||||||
|
<!-- <row>
|
||||||
|
<entry><para>OVM</para></entry>
|
||||||
|
<entry><para>RAW</para></entry>
|
||||||
|
</row> -->
|
||||||
|
</tbody>
|
||||||
|
</tgroup>
|
||||||
|
</informaltable>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>URL. The secure HTTP or HTTPS URL that &PRODUCT; can use to access your disk. The
|
||||||
|
type of file at the URL must match the value chosen in Format. For example, if Format is
|
||||||
|
VHD, the URL might look like the following:</para>
|
||||||
|
<para>http://yourFileServerIP/userdata/myDataDisk.vhd</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>MD5 checksum. (Optional) Use the hash that you created in step 1.</para>
|
||||||
|
</listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>Wait until the status of the volume shows that the upload is complete. Click Instances -
|
||||||
|
Volumes, find the name you specified in step 5, and make sure the status is Uploaded.</para>
|
||||||
|
</listitem>
|
||||||
|
</orderedlist>
|
||||||
|
>>>>>>> 9cb9f45... CLOUDSTACK-1313
|
||||||
</section>
|
</section>
|
||||||
|
|||||||
@ -24,12 +24,17 @@
|
|||||||
<section id="vm-storage-migration">
|
<section id="vm-storage-migration">
|
||||||
<title>VM Storage Migration</title>
|
<title>VM Storage Migration</title>
|
||||||
<para>Supported in XenServer, KVM, and VMware.</para>
|
<para>Supported in XenServer, KVM, and VMware.</para>
|
||||||
<note><para>This procedure is different from moving disk volumes from one VM to another. See Detaching and Moving Volumes <xref linkend="detach-move-volumes" />.</para>
|
<note>
|
||||||
|
<para>This procedure is different from moving disk volumes from one VM to another. See Detaching
|
||||||
|
and Moving Volumes <xref linkend="detach-move-volumes"/>.</para>
|
||||||
</note>
|
</note>
|
||||||
<para></para>
|
<para>You can migrate a virtual machine’s root disk volume or any additional data disk volume from
|
||||||
<para>You can migrate a virtual machine’s root disk volume or any additional data disk volume from one storage pool to another in the same zone.</para>
|
one storage pool to another in the same zone.</para>
|
||||||
<para>You can use the storage migration feature to achieve some commonly desired administration goals, such as balancing the load on storage pools and increasing the reliability of virtual machines by moving them away from any storage pool that is experiencing issues.</para>
|
<para>You can use the storage migration feature to achieve some commonly desired administration
|
||||||
<xi:include href="migrate-datadisk-volume-new-storage-pool.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
goals, such as balancing the load on storage pools and increasing the reliability of virtual
|
||||||
<xi:include href="migrate-vm-rootvolume-volume-new-storage-pool.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
|
machines by moving them away from any storage pool that is experiencing issues.</para>
|
||||||
|
<xi:include href="migrate-datadisk-volume-new-storage-pool.xml"
|
||||||
|
xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
|
<xi:include href="migrate-vm-rootvolume-volume-new-storage-pool.xml"
|
||||||
|
xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|||||||
@ -21,15 +21,24 @@
|
|||||||
specific language governing permissions and limitations
|
specific language governing permissions and limitations
|
||||||
under the License.
|
under the License.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<section id="volume-deletion-garbage-collection">
|
<section id="volume-deletion-garbage-collection">
|
||||||
<title>Volume Deletion and Garbage Collection</title>
|
<title>Volume Deletion and Garbage Collection</title>
|
||||||
<para>The deletion of a volume does not delete the snapshots that have been created from the volume</para>
|
<para>The deletion of a volume does not delete the snapshots that have been created from the
|
||||||
<para>When a VM is destroyed, data disk volumes that are attached to the VM are not deleted.</para>
|
volume</para>
|
||||||
<para>Volumes are permanently destroyed using a garbage collection process. The global configuration variables expunge.delay and expunge.interval determine when the physical deletion of volumes will occur.</para>
|
<para>When a VM is destroyed, data disk volumes that are attached to the VM are not
|
||||||
|
deleted.</para>
|
||||||
|
<para>Volumes are permanently destroyed using a garbage collection process. The global
|
||||||
|
configuration variables expunge.delay and expunge.interval determine when the physical deletion
|
||||||
|
of volumes will occur.</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>expunge.delay: determines how old the volume must be before it is destroyed, in seconds</para></listitem>
|
<listitem>
|
||||||
<listitem><para>expunge.interval: determines how often to run the garbage collection check</para></listitem>
|
<para>expunge.delay: determines how old the volume must be before it is destroyed, in
|
||||||
|
seconds</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>expunge.interval: determines how often to run the garbage collection check</para>
|
||||||
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
<para>Administrators should adjust these values depending on site policies around data retention.</para>
|
<para>Administrators should adjust these values depending on site policies around data
|
||||||
|
retention.</para>
|
||||||
</section>
|
</section>
|
||||||
|
|||||||
@ -21,29 +21,32 @@
|
|||||||
specific language governing permissions and limitations
|
specific language governing permissions and limitations
|
||||||
under the License.
|
under the License.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<section id="working-with-volumes">
|
<section id="working-with-volumes">
|
||||||
<title>Using Swift for Secondary Storage</title>
|
<title>Working With Volumes</title>
|
||||||
<para>A volume provides storage to a guest VM. The volume can provide for
|
<para>A volume provides storage to a guest VM. The volume can provide for a root disk or an
|
||||||
a root disk or an additional data disk. &PRODUCT; supports additional
|
additional data disk. &PRODUCT; supports additional volumes for guest VMs. </para>
|
||||||
volumes for guest VMs.
|
<para>Volumes are created for a specific hypervisor type. A volume that has been attached to guest
|
||||||
</para>
|
using one hypervisor type (e.g, XenServer) may not be attached to a guest that is using another
|
||||||
<para>Volumes are created for a specific hypervisor type. A volume that has
|
hypervisor type, for example:vSphere, KVM. This is because the different hypervisors use different
|
||||||
been attached to guest using one hypervisor type (e.g, XenServer) may not
|
disk image formats. </para>
|
||||||
be attached to a guest that is using another hypervisor type (e.g.
|
<para>&PRODUCT; defines a volume as a unit of storage available to a guest VM. Volumes are either
|
||||||
vSphere, KVM). This is because the different hypervisors use
|
root disks or data disks. The root disk has "/" in the file system and is usually the boot
|
||||||
different disk image formats.
|
device. Data disks provide for additional storage, for example: "/opt" or "D:". Every guest VM
|
||||||
</para>
|
has a root disk, and VMs can also optionally have a data disk. End users can mount multiple data
|
||||||
<para>&PRODUCT; defines a volume as a unit of storage available to a guest
|
disks to guest VMs. Users choose data disks from the disk offerings created by administrators.
|
||||||
VM. Volumes are either root disks or data disks. The root disk has "/"
|
The user can create a template from a volume as well; this is the standard procedure for private
|
||||||
in the file system and is usually the boot device. Data disks provide
|
template creation. Volumes are hypervisor-specific: a volume from one hypervisor type may not be
|
||||||
for additional storage (e.g. As "/opt" or "D:"). Every guest VM has a root
|
used on a guest of another hypervisor type. </para>
|
||||||
disk, and VMs can also optionally have a data disk. End users can mount
|
<note>
|
||||||
multiple data disks to guest VMs. Users choose data disks from the disk
|
<para>&PRODUCT; supports attaching up to 13 data disks to a VM on XenServer hypervisor versions
|
||||||
offerings created by administrators. The user can create a template from
|
6.0 and above. For the VMs on other hypervisor types, the data disk limit is 6.</para>
|
||||||
a volume as well; this is the standard procedure for private template
|
</note>
|
||||||
creation. Volumes are hypervisor-specific: a volume from one hypervisor
|
<xi:include href="creating-new-volumes.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
type may not be used on a guest of another hypervisor type.
|
<xi:include href="upload-existing-volume-to-vm.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
</para>
|
<xi:include href="attaching-volume.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
|
<xi:include href="detach-move-volumes.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
|
<xi:include href="vm-storage-migration.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
|
<xi:include href="resizing-volumes.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
|
<xi:include href="volume-deletion-garbage-collection.xml"
|
||||||
|
xmlns:xi="http://www.w3.org/2001/XInclude"/>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user