openstack/openstack-manuals
Code Issues Proposed changes

minor cleanup to ch_openstack_images

Browse Source 
removed create, create add together doesn't make sense
removed incomplete sentence

Change-Id: Ic195901b07a358812857bc2b7d542543a0c2fdae
This commit is contained in:
Shilla Saebi 2014-02-17 14:56:56 -05:00
parent 7048c6ffe5
commit cbf9984bc6
1 changed files with 254 additions and 226 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

480
doc/image-guide/ch_openstack_images.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter xmlns="http://docbook.org/ns/docbook" <chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
@ -10,125 +14,131 @@
some of these, the requirement can be fulfilled by installing some of these, the requirement can be fulfilled by installing
the <link the <link
xlink:href="https://cloudinit.readthedocs.org/en/latest/" xlink:href="https://cloudinit.readthedocs.org/en/latest/"
>cloud-init</link> package. You should read this section ><package>cloud-init</package></link> package. Read
before creating your own image to be sure that the image this section before you create your own image to be sure that
supports the OpenStack features you plan on using.<itemizedlist> the image supports the OpenStack features that you plan on
<listitem> using.</para>
<para>Disk partitions and resize root partition on <itemizedlist>
boot (cloud-init)</para> <listitem>
</listitem> <para>Disk partitions and resize root partition on boot
<listitem> (<package>cloud-init</package>)</para>
<para>No hard-coded MAC address information</para> </listitem>
</listitem> <listitem>
<listitem> <para>No hard-coded MAC address information</para>
<para>SSH server running</para> </listitem>
</listitem> <listitem>
<listitem> <para>SSH server running</para>
<para>Disable firewall</para> </listitem>
</listitem> <listitem>
<listitem> <para>Disable firewall</para>
<para>Access instance using ssh public key </listitem>
(cloud-init)</para> <listitem>
</listitem> <para>Access instance using ssh public key
<listitem> (<package>cloud-init</package>)</para>
<para>Process user data and other metadata </listitem>
(cloud-init)</para> <listitem>
</listitem> <para>Process user data and other metadata
<listitem> (<package>cloud-init</package>)</para>
<para>Paravirtualized Xen support in Linux kernel (Xen </listitem>
hypervisor only with Linux kernel version &lt; <listitem>
3.0)</para> <para>Paravirtualized Xen support in Linux kernel (Xen
</listitem> hypervisor only with Linux kernel version &lt;
</itemizedlist></para> 3.0)</para>
</listitem>
</itemizedlist>
<section xml:id="support-resizing"> <section xml:id="support-resizing">
<title>Disk partitions and resize root partition on boot <title>Disk partitions and resize root partition on boot
(cloud-init)</title> (cloud-init)</title>
<para>When you create a new Linux image, the first decision <para>When you create a Linux image, you must decide how to
you will need to make is how to partition the disks. The partition the disks. The choice of partition method can
choice of partition method can affect the resizing affect the resizing functionality, as described in the
functionality, as described below.</para> following sections.</para>
<para>The size of the disk in a virtual machine image is <para>The size of the disk in a virtual machine image is
determined when you initially create the image. However, determined when you initially create the image. However,
OpenStack lets you launch instances with different size OpenStack lets you launch instances with different size
drives by specifying different flavors. For example, if drives by specifying different flavors. For example, if
your image was created with a 5 GB disk, and you launch an your image was created with a 5&nbsp;GB disk, and you
instance with a flavor of <literal>m1.small</literal>. The launch an instance with a flavor of
resulting virtual machine instance has, by default, <literal>m1.small</literal>. The resulting virtual
a primary disk size of 10 GB. When an instance's disk is resized machine instance has, by default, a primary disk size of
up, zeros are just added to the end.</para> 10&nbsp;GB. When the disk for an instance is resized up,
<para>Your image needs to be able to resize its partitions on zeros are just added to the end.</para>
boot to match the size requested by the user. Otherwise, <para>Your image must be able to resize its partitions on boot
after the instance boots, you will need to manually resize to match the size requested by the user. Otherwise, after
the partitions if you want to access the additional the instance boots, you must manually resize the
storage you have access to when the disk size associated partitions to access the additional storage to which you
with the flavor exceeds the disk size your image was have access when the disk size associated with the flavor
created with.</para> exceeds the disk size with which your image was
created.</para>
<simplesect> <simplesect>
<title>Xen: 1 ext3/ext4 partition (no LVM, no /boot, no <title>Xen: 1 ext3/ext4 partition (no LVM, no /boot, no
swap)</title> swap)</title>
<para>If you are using the OpenStack XenAPI driver, the <para>If you use the OpenStack XenAPI driver, the Compute
Compute service will automatically adjust the service automatically adjusts the partition and file
partition and filesystem for your instance on boot. system for your instance on boot. Automatic resize
Automatic resize will occur if the following are all true:<itemizedlist> occurs if the following conditions are all
<listitem> true:</para>
<para><literal>auto_disk_config=True</literal> <itemizedlist>
is set as a property on the image in the <listitem>
Image Registry.</para> <para><literal>auto_disk_config=True</literal> is
</listitem> set as a property on the image in the image
<listitem> registry.</para>
<para>The disk on the image has only one </listitem>
partition.</para> <listitem>
</listitem> <para>The disk on the image has only one
<listitem> partition.</para>
<para>The file system on the one partition is </listitem>
ext3 or ext4.</para> <listitem>
</listitem> <para>The file system on the one partition is ext3
</itemizedlist></para> or ext4.</para>
<para>Therefore, if you are using Xen, we recommend that </listitem>
when you create your images, you create a single ext3 </itemizedlist>
or ext4 partition (not managed by LVM). Otherwise, <para>Therefore, if you use Xen, we recommend that when
read on.</para> you create your images, you create a single ext3 or
ext4 partition (not managed by LVM). Otherwise, read
on.</para>
</simplesect> </simplesect>
<simplesect> <simplesect>
<title>Non-Xen with cloud-init/cloud-tools: 1 ext3/ext4 <title>Non-Xen with cloud-init/cloud-tools: One ext3/ext4
partition (no LVM, no /boot, no swap)</title> partition (no LVM, no /boot, no swap)</title>
<para>Your image must be configured to deal with two issues:<itemizedlist> <para>You must configure these items for your
<listitem> image:</para>
<para>The image's partition table describes <itemizedlist>
the original size of the image</para> <listitem>
</listitem> <para>The partition table for the image describes
<listitem> the original size of the image</para>
<para>The image's filesystem fills the </listitem>
original size of the image</para> <listitem>
</listitem> <para>The file system for the image fills the
</itemizedlist></para> original size of the image</para>
<para>Then, during the boot process:<itemizedlist> </listitem>
<listitem> </itemizedlist>
<para>the partition table must be modified to <para>Then, during the boot process, you must:</para>
be made aware of the additional space<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>If you are not using LVM, you <para>Modify the partition table to make it aware
must modify the table to extend the of the additional space:</para>
existing root partition to <itemizedlist>
encompass this additional <listitem>
space</para> <para>If you do not use LVM, you must
</listitem> modify the table to extend the
<listitem> existing root partition to encompass
<para>If you are using LVM, you can this additional space.</para>
create add a new LVM entry to the </listitem>
partition table, create a new LVM <listitem>
physical volume, add it to the <para>If you use LVM, you can add a new
volume group, and extend the LVM entry to the partition table,
logical partition with the root create a new LVM physical volume, add
volume</para> it to the volume group, and extend the
</listitem> logical partition with the root
</itemizedlist></para> volume.</para>
</listitem> </listitem>
<listitem> </itemizedlist>
<para>the root volume filesystem must be </listitem>
resized</para> <listitem>
</listitem> <para>Resize the root volume file system.</para>
</itemizedlist></para> </listitem>
</itemizedlist>
<para>The simplest way to support this in your image is to <para>The simplest way to support this in your image is to
install the <link install the <link
xlink:href="https://launchpad.net/cloud-utils" xlink:href="https://launchpad.net/cloud-utils"
@ -136,42 +146,46 @@
<command>growpart</command> tool for extending <command>growpart</command> tool for extending
partitions), the <link partitions), the <link
xlink:href="https://launchpad.net/cloud-initramfs-tools" xlink:href="https://launchpad.net/cloud-initramfs-tools"
>cloud-initramfs-tools</link> package (which will >cloud-initramfs-tools</link> package (which
support resizing root partition on the first boot), supports resizing root partition on the first boot),
and the <link and the <link
xlink:href="https://launchpad.net/cloud-init" xlink:href="https://launchpad.net/cloud-init"
>cloud-init</link> package into your image. With ><package>cloud-init</package></link> package
these installed, the image will perform the root into your image. With these installed, the image
partition resize on boot. For example, in the performs the root partition resize on boot. For
<filename>/etc/rc.local</filename> file. These example, in the <filename>/etc/rc.local</filename>
packages are in the Ubuntu and Debian package file. These packages are in the Ubuntu and Debian
repository, as well as the EPEL repository (for package repository, as well as the EPEL repository
Fedora/RHEL/CentOS/Scientific Linux guests).</para> (for Fedora/RHEL/CentOS/Scientific Linux
<para>If you are not able to install guests).</para>
<para>If you cannot install
<literal>cloud-initramfs-tools</literal>, Robert <literal>cloud-initramfs-tools</literal>, Robert
Plestenjak has a github project called <link Plestenjak has a github project called <link
xlink:href="https://github.com/flegmatik/linux-rootfs-resize" xlink:href="https://github.com/flegmatik/linux-rootfs-resize"
>linux-rootfs-resize</link> that contains scripts >linux-rootfs-resize</link> that contains scripts
that will update a ramdisk using that update a ramdisk by using
<command>growpart</command> so that the image will <command>growpart</command> so that the image
resize properly on boot.</para> resizes properly on boot.</para>
<para>If you are able to install the cloud-utils and <para>If you can install the cloud-utils and
cloud-init packages, we recommend that when you create <package>cloud-init</package> packages, we
your images, you create a single ext3 or ext4 recommend that when you create your images, you create
partition (not managed by LVM).</para> a single ext3 or ext4 partition (not managed by
LVM).</para>
</simplesect> </simplesect>
<simplesect> <simplesect>
<title>Non-Xen without cloud-init/cloud-tools: LVM</title> <title>Non-Xen without
<para>If you cannot install cloud-init and cloud-tools <package>cloud-init</package>/<package>cloud-tools</package>:
inside of your guest, and you want to support resize, LVM</title>
you will need to write a script that your image will <para>If you cannot install <package>cloud-init</package>
run on boot to modify the partition table. In this and <package>cloud-tools</package> inside of your
case, we recommend using LVM to manage your guest, and you want to support resize, you must write
partitions. Due to a limitation in the Linux kernel a script that your image runs on boot to modify the
(as of this writing), you cannot modify a partition partition table. In this case, we recommend using LVM
table of a raw disk that has partition currently to manage your partitions. Due to a limitation in the
mounted, but you can do this for LVM.</para> Linux kernel (as of this writing), you cannot modify a
<para>Your script will need to do something like the following:<orderedlist> partition table of a raw disk that has partitions
currently mounted, but you can do this for LVM.</para>
<para>Your script must do something like the following:<orderedlist>
<listitem> <listitem>
<para>Detect if any additional space is <para>Detect if any additional space is
available on the disk. For example, parse available on the disk. For example, parse
@ -210,58 +224,56 @@
/dev/mapper/<replaceable>node-root</replaceable></command>.</para> /dev/mapper/<replaceable>node-root</replaceable></command>.</para>
</listitem> </listitem>
</orderedlist></para> </orderedlist></para>
<para>You do not need to have a <filename>/boot</filename> <para>You do not need a <filename>/boot</filename>
partition, unless your image is an older Linux partition unless your image is an older Linux
distribution that requires that distribution that requires that
<filename>/boot</filename> is not managed by LVM. <filename>/boot</filename> is not managed by LVM.</para>
You may elect to use a swap per</para>
</simplesect> </simplesect>
</section> </section>
<section xml:id="mac-adddress"> <section xml:id="mac-adddress">
<title>No hard-coded MAC address information</title> <title>No hard-coded MAC address information</title>
<para>You must remove the network persistence rules in the <para>You must remove the network persistence rules in the
image as their presence will result in the network image because they cause the network interface in the
interface in the instance coming up as an interface other instance to come up as an interface other than eth0. This
than eth0. This is because your image has a record of the is because your image has a record of the MAC address of
MAC address of the network interface card when it was the network interface card when it was first installed,
first installed, and this MAC address will be different and this MAC address is different each time that the
each time the instance boots up. You should alter the instance boots. You should alter the following
following files:<itemizedlist> files:</para>
<listitem> <itemizedlist>
<para>Replace <listitem>
<filename>/etc/udev/rules.d/70-persistent-net.rules</filename> <para>Replace
with an empty file (contains network <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>
persistence rules, including MAC with an empty file (contains network persistence
address)</para> rules, including MAC address)</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Replace <para>Replace
<filename>/lib/udev/rules.d/75-persistent-net-generator.rules</filename> <filename>/lib/udev/rules.d/75-persistent-net-generator.rules</filename>
with an empty file (this generates the file with an empty file (this generates the file
above)</para> above)</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Remove the HWADDR line from <para>Remove the HWADDR line from
<filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename>
on Fedora-based images</para> on Fedora-based images</para>
</listitem> </listitem>
</itemizedlist><note> </itemizedlist>
<para>If you delete the network persistent rules <note>
files, you may get a udev kernel warning at boot <para>If you delete the network persistent rules files,
time, which is why we recommend replacing them you may get a udev kernel warning at boot time, which
with empty files instead.</para> is why we recommend replacing them with empty files
</note></para> instead.</para>
</note>
</section> </section>
<section xml:id="ensure-ssh-server"> <section xml:id="ensure-ssh-server">
<title>Ensure ssh server runs</title> <title>Ensure ssh server runs</title>
<para>You must install an ssh server into the image and ensure <para>You must install an ssh server into the image and ensure
that it starts up on boot, or you will not be able to that it starts up on boot, or you cannot connect to your
connect to your instance using ssh when it boots inside of instance by using ssh when it boots inside of OpenStack.
OpenStack. This package is typically called This package is typically called
<literal>openssh-server</literal>.</para> <literal>openssh-server</literal>.</para>
</section> </section>
<section xml:id="disable-firewall"> <section xml:id="disable-firewall">
<title>Disable firewall</title> <title>Disable firewall</title>
<para>In general, we recommend that you disable any firewalls <para>In general, we recommend that you disable any firewalls
@ -272,7 +284,7 @@
connect to your instance.</para> connect to your instance.</para>
</section> </section>
<section xml:id="ssh-public-key"> <section xml:id="ssh-public-key">
<title>Access instance using ssh public key <title>Access instance by using ssh public key
(cloud-init)</title> (cloud-init)</title>
<para>The typical way that users access virtual machines <para>The typical way that users access virtual machines
running on OpenStack is to ssh using public key running on OpenStack is to ssh using public key
@ -281,28 +293,32 @@
from the OpenStack metadata service or config drive, at from the OpenStack metadata service or config drive, at
boot time.</para> boot time.</para>
<simplesect> <simplesect>
<title>Use cloud-init to fetch the public key</title> <title>Use <package>cloud-init</package> to fetch the
<para>The cloud-init package will automatically fetch the public key</title>
public key from the metadata server and place the key <para>The <package>cloud-init</package> package
in an account. The account varies by distribution. On automatically fetches the public key from the metadata
Ubuntu-based virtual machines, the account is called server and places the key in an account. The account
"ubuntu". On Fedora-based virtual machines, the varies by distribution. On Ubuntu-based virtual
account is called "ec2-user".</para> machines, the account is called
<literal>ubuntu</literal>. On Fedora-based virtual
machines, the account is called
<literal>ec2-user</literal>.</para>
<para>You can change the name of the account used by <para>You can change the name of the account used by
cloud-init by editing the <package>cloud-init</package> by editing the
<filename>/etc/cloud/cloud.cfg</filename> file and <filename>/etc/cloud/cloud.cfg</filename> file and
adding a line with a different user. For example, to adding a line with a different user. For example, to
configure cloud-init to put the key in an account configure <package>cloud-init</package> to put the key
named <literal>admin</literal>, edit the configuration in an account named <literal>admin</literal>, edit the
file so it has the line:</para> configuration file so it has the line:</para>
<programlisting>user: admin</programlisting> <programlisting>user: admin</programlisting>
</simplesect> </simplesect>
<simplesect> <simplesect>
<title>Write a custom script to fetch the public <title>Write a custom script to fetch the public
key</title> key</title>
<para>If you are unable or unwilling to install cloud-init <para>If you are unable or unwilling to install
inside the guest, you can write a custom script to <package>cloud-init</package> inside the guest,
fetch the public key and add it to a user account.</para> you can write a custom script to fetch the public key
and add it to a user account.</para>
<para>To fetch the ssh public key and add it to the root <para>To fetch the ssh public key and add it to the root
account, edit the <filename>/etc/rc.local</filename> account, edit the <filename>/etc/rc.local</filename>
file and add the following lines before the line file and add the following lines before the line
@ -357,17 +373,16 @@ done</programlisting>
<section xml:id="metadata"> <section xml:id="metadata">
<title>Process user data and other metadata <title>Process user data and other metadata
(cloud-init)</title> (cloud-init)</title>
<para>In addition to the ssh public key, an image may need to <para>In addition to the ssh public key, an image might need
retrieve additional information from OpenStack, such as additional information from OpenStack, such as <link
<link
xlink:href="http://docs.openstack.org/user-guide/content/user-data.html" xlink:href="http://docs.openstack.org/user-guide/content/user-data.html"
>user data</link> that the user submitted when >user data</link> that the user submitted when
requesting the image. For example, you might want to set the requesting the image. For example, you might want to set
host name of the instance when it is booted. Or, you might the host name of the instance when it is booted. Or, you
wish to configure your image so that it executes user data might wish to configure your image so that it executes
content as a script on boot.</para> user data content as a script on boot.</para>
<para>This information is accessible through the metadata service <para>This information is accessible through the metadata
or the <link service or the <link
xlink:href="http://docs.openstack.org/user-guide/content/config-drive.html" xlink:href="http://docs.openstack.org/user-guide/content/config-drive.html"
>config drive</link>. As the OpenStack metadata >config drive</link>. As the OpenStack metadata
service is compatible with version 2009-04-04 of the service is compatible with version 2009-04-04 of the
@ -378,9 +393,10 @@ done</programlisting>
retrieve user data.</para> retrieve user data.</para>
<para>The easiest way to support this type of functionality is <para>The easiest way to support this type of functionality is
to install the cloud-init package into your image, which to install the <package>cloud-init</package> package into
is configured by default to treat user data as an your image, which is configured by default to treat user
executable script, and will set the host name.</para> data as an executable script, and sets the host
name.</para>
</section> </section>
<section xml:id="write-to-console"> <section xml:id="write-to-console">
<title>Ensure image writes boot log to console</title> <title>Ensure image writes boot log to console</title>
@ -394,11 +410,12 @@ done</programlisting>
looks something like this:</para> looks something like this:</para>
<programlisting>linux /boot/vmlinuz-3.2.0-49-virtual root=UUID=6d2231e4-0975-4f35-a94f-56738c1a8150 ro console=ttyS0</programlisting> <programlisting>linux /boot/vmlinuz-3.2.0-49-virtual root=UUID=6d2231e4-0975-4f35-a94f-56738c1a8150 ro console=ttyS0</programlisting>
<para>If <literal>console=ttyS0</literal> does not appear, you <para>If <literal>console=ttyS0</literal> does not appear, you
will need to modify your grub configuration. In general, must modify your grub configuration. In general, you
you should not update the grub.cfg directly, since it is should not update the <filename>grub.cfg</filename>
automatically generated. Instead, you should edit directly, since it is automatically generated. Instead,
<filename>/etc/default/grub</filename> and modify the you should edit <filename>/etc/default/grub</filename> and
value of the <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> modify the value of the
<literal>GRUB_CMDLINE_LINUX_DEFAULT</literal>
variable: variable:
<programlisting language="bash">GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0"</programlisting></para> <programlisting language="bash">GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0"</programlisting></para>
<para>Next, update the grub configuration. On Debian-based <para>Next, update the grub configuration. On Debian-based
@ -417,8 +434,8 @@ done</programlisting>
guests). If you are running the Xen hypervisor with guests). If you are running the Xen hypervisor with
paravirtualization, and you want to create an image for an paravirtualization, and you want to create an image for an
older Linux distribution that has a pre 3.0 kernel, you older Linux distribution that has a pre 3.0 kernel, you
will need to ensure that the image boots a kernel that has must ensure that the image boots a kernel that has been
been compiled with Xen support.</para> compiled with Xen support.</para>
</section> </section>
<section xml:id="image-cache-management"> <section xml:id="image-cache-management">
<title>Manage the image cache</title> <title>Manage the image cache</title>
@ -429,8 +446,8 @@ done</programlisting>
compute nodes share one common compute nodes share one common
<filename>/var/lib/nova/instances/</filename> <filename>/var/lib/nova/instances/</filename>
directory.</para> directory.</para>
<para>For information about libvirt images in OpenStack, refer <para>For information about libvirt images in OpenStack, see
to <link <link
xlink:href="http://www.pixelbeat.org/docs/openstack_libvirt_images/" xlink:href="http://www.pixelbeat.org/docs/openstack_libvirt_images/"
>The life of an OpenStack libvirt image from Pádraig >The life of an OpenStack libvirt image from Pádraig
Brady</link>.</para> Brady</link>.</para>
@ -448,18 +465,29 @@ done</programlisting>
<tbody> <tbody>
<tr> <tr>
<td>preallocate_images=none</td> <td>preallocate_images=none</td>
<td>(StrOpt) VM image preallocation mode: "none" <td><para>(StrOpt) VM image preallocation
=&gt; no storage provisioning is done up mode:</para><itemizedlist>
front, "space" =&gt; storage is fully <listitem>
allocated at instance start. If this is set to <para><literal>none</literal>. No
'space', the $instance_dir/ images will be  storage provisioning occurs up
<link front.</para>
xlink:href="http://www.kernel.org/doc/man-pages/online/pages/man2/fallocate.2.html" </listitem>
>fallocate</link>d to immediately <listitem>
determine if enough space is available, and to <para><literal>space</literal>.
possibly improve VM I/O performance due to Storage is fully allocated at
ongoing allocation avoidance, and better instance start. The
locality of block allocations.</td> <literal>$instance_dir/</literal>
images are <link
xlink:href="http://www.kernel.org/doc/man-pages/online/pages/man2/fallocate.2.html"
>fallocate</link>d to immediately
determine if enough space is
available, and to possibly improve
VM I/O performance due to ongoing
allocation avoidance, and better
locality of block
allocations.</para>
</listitem>
</itemizedlist></td>
</tr> </tr>
<tr> <tr>
<td>remove_unused_base_images=True</td> <td>remove_unused_base_images=True</td>
@ -472,13 +500,13 @@ done</programlisting>
<tr> <tr>
<td>remove_unused_original_minimum_age_seconds=86400</td> <td>remove_unused_original_minimum_age_seconds=86400</td>
<td>(IntOpt) Unused unresized base images younger <td>(IntOpt) Unused unresized base images younger
than this will not be removed. Default is than this are not removed. Default is 86400
86400 seconds, or 24 hours.</td> seconds, or 24 hours.</td>
</tr> </tr>
<tr> <tr>
<td>remove_unused_resized_minimum_age_seconds=3600</td> <td>remove_unused_resized_minimum_age_seconds=3600</td>
<td>(IntOpt) Unused resized base images younger <td>(IntOpt) Unused resized base images younger
than this will not be removed. Default is 3600 than this are not removed. Default is 3600
seconds, or one hour.</td> seconds, or one hour.</td>
</tr> </tr>
</tbody> </tbody>
@ -494,7 +522,7 @@ a0d1d5d3_20
2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removable base files: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810 2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removable base files: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810
a0d1d5d3 /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810a0d1d5d3_20 a0d1d5d3 /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810a0d1d5d3_20
2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removing base file: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810a0d1d5d3</computeroutput></screen> 2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removing base file: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810a0d1d5d3</computeroutput></screen>
<para>Since 86400 seconds (24 hours) is the default time for <para>Because 86400 seconds (24 hours) is the default time for
<literal>remove_unused_original_minimum_age_seconds</literal>, <literal>remove_unused_original_minimum_age_seconds</literal>,
you can either wait for that time interval to see the base you can either wait for that time interval to see the base
image removed, or set the value to a shorter time period image removed, or set the value to a shorter time period