msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-04-19 06:23+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ./doc/image-guide/ch_modifying_images.xml:10(title)
msgid "Modify images"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:16(para)
msgid "Do not attempt to use these tools to modify an image that is attached to a running virtual machine. These tools are designed to only modify images that are not currently running."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:12(para)
msgid "Once you have obtained a virtual machine image, you may want to make some changes to it before uploading it to the OpenStack Image Service. Here we describe several tools available that allow you to modify images.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:22(title)
msgid "guestfish"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:23(para)
msgid "The <placeholder-1/> program is a tool from the <link href=\"http://libguestfs.org/\">libguestfs</link> project that allows you to modify the files inside of a virtual machine image."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:28(para)
msgid "<placeholder-1/> does not mount the image directly into the local file system. Instead, it provides you with a shell interface that enables you to view, edit, and delete files. Many of <placeholder-2/> commands, such as <placeholder-3/>, <placeholder-4/>, and <placeholder-5/>, resemble traditional bash commands."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:38(title)
msgid "Example guestfish session"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:39(para)
msgid "Sometimes, you must modify a virtual machine image to remove any traces of the MAC address that was assigned to the virtual network interface card when the image was first created, because the MAC address will be different when it boots the next time. This example shows how to use guestfish to remove references to the old MAC address by deleting the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file and removing the <literal>HWADDR</literal> line from the <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> file."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:51(para)
msgid "Assume that you have a CentOS qcow2 image called <filename>centos63_desktop.img</filename>. Mount the image in read-write mode as root, as follows:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:65(para)
msgid "This starts a guestfish session. Note that the guestfish prompt looks like a fish: <literal>&gt; &lt;fs&gt;</literal>."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:68(para)
msgid "We must first use the <placeholder-1/> command at the guestfish prompt before we can do anything else. This will launch a virtual machine, which will be used to perform all of the file manipulations.<placeholder-2/> We can now view the file systems in the image using the <placeholder-3/> command:<placeholder-4/>We need to mount the logical volume that contains the root partition: <placeholder-5/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:82(para)
msgid "Next, we want to delete a file. We can use the <placeholder-1/> guestfish command, which works the same way it does in a traditional shell."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:86(para)
msgid "<placeholder-1/>We want to edit the <filename>ifcfg-eth0</filename> file to remove the <literal>HWADDR</literal> line. The <placeholder-2/> command will copy the file to the host, invoke your editor, and then copy the file back. <placeholder-3/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:93(para)
msgid "If you want to modify this image to load the 8021q kernel at boot time, you must create an executable script in the <filename>/etc/sysconfig/modules/</filename> directory. You can use the <placeholder-1/> guestfish command to create an empty file, the <placeholder-2/> command to edit it, and the <placeholder-3/> command to make it executable.<placeholder-4/> We add the following line to the file and save it:<placeholder-5/>Then we set to executable: <placeholder-6/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:107(para)
msgid "We're done, so we can exit using the <placeholder-1/> command:<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:112(title)
msgid "Go further with guestfish"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:113(para)
msgid "There is an enormous amount of functionality in guestfish and a full treatment is beyond the scope of this document. Instead, we recommend that you read the <link href=\"http://libguestfs.org/guestfs-recipes.1.html\">guestfs-recipes</link> documentation page for a sense of what is possible with these tools."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:123(title)
msgid "guestmount"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:124(para)
msgid "For some types of changes, you may find it easier to mount the image's file system directly in the guest. The <placeholder-1/> program, also from the libguestfs project, allows you to do so."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:128(para)
msgid "For example, to mount the root partition from our <filename>centos63_desktop.qcow2</filename> image to <filename>/mnt</filename>, we can do:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:134(para)
msgid "If we didn't know in advance what the mount point is in the guest, we could use the <literal>-i</literal>(inspect) flag to tell guestmount to automatically determine what mount point to use:<placeholder-1/>Once mounted, we could do things like list the installed packages using rpm:<placeholder-2/> Once done, we unmount:<placeholder-3/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:146(title)
msgid "virt-* tools"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:151(para)
msgid "<link href=\"http://libguestfs.org/virt-edit.1.html\">virt-edit</link> for editing a file inside of an image."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:157(para)
msgid "<link href=\"http://libguestfs.org/virt-df.1.html\">virt-df</link> for displaying free space inside of an image."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:163(para)
msgid "<link href=\"http://libguestfs.org/virt-resize.1.html\">virt-resize</link> for resizing an image."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:169(para)
msgid "<link href=\"http://libguestfs.org/virt-sysprep.1.html\">virt-sysprep</link> for preparing an image for distribution (for example, delete SSH host keys, remove MAC address info, or remove user accounts)."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:177(para)
msgid "<link href=\"http://libguestfs.org/virt-sparsify.1.html\">virt-sparsify</link> for making an image sparse"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:183(para)
msgid "<link href=\"http://libguestfs.org/virt-v2v/\">virt-p2v</link> for converting a physical machine to an image that runs on KVM"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:189(para)
msgid "<link href=\"http://libguestfs.org/virt-v2v/\">virt-v2v</link> for converting Xen and VMWare images to KVM images"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:147(para)
msgid "The <link href=\"http://libguestfs.org/\">libguestfs</link> project has a number of other useful tools, including:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:196(title)
msgid "Modify a single file inside of an image"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:197(para)
msgid "This example shows how to use <placeholder-1/> to modify a file. The command can take either a filename as an argument with the <literal>-a</literal> flag, or a domain name as an argument with the <literal>-d</literal> flag. The following examples shows how to use this to modify the <filename>/etc/shadow</filename> file in instance with libvirt domain name <literal>instance-000000e1</literal> that is currently running:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:214(title)
msgid "Resize an image"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:215(para)
msgid "Here's a simple of example of how to use <placeholder-1/> to resize an image. Assume we have a 16 GB Windows image in qcow2 format that we want to resize to 50 GB. First, we use <placeholder-2/> to identify the partitions:<placeholder-3/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:227(para)
msgid "In this case, it's the <filename>/dev/sda2</filename> partition that we want to resize. We create a new qcow2 image and use the <placeholder-1/> command to write a resized copy of the original into the new image: <placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:261(title)
msgid "Loop devices, kpartx, network block devices"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:265(para)
msgid "Mounting untrusted guest images using the tools described in this section is a security risk, always use libguestfs tools such as guestfish and guestmount if you have access to them. See <link href=\"https://www.berrange.com/posts/2013/02/20/a-reminder-why-you-should-never-mount-guest-disk-images-on-the-host-os/\">A reminder why you should never mount guest disk images on the host OS</link> by Daniel Berrangé for more details."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:262(para)
msgid "If you don't have access to libguestfs, you can mount image file systems directly in the host using loop devices, kpartx, and network block devices.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:275(title)
msgid "Mount a raw image (without LVM)"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:276(para)
msgid "If you have a raw virtual machine image that is not using LVM to manage its partitions. First, use the <placeholder-1/> command to find an unused loop device. <placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:282(para)
msgid "In this example, <filename>/dev/loop0</filename> is free. Associate a loop device with the raw image:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:285(para)
msgid "If the image only has a single partition, you can mount the loop device directly:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:288(para)
msgid "If the image has multiple partitions, use <placeholder-1/> to expose the partitions as separate devices (for example, <filename>/dev/mapper/loop0p1</filename>), then mount the partition that corresponds to the root file system:<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:294(para)
msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created per partition:<placeholder-1/>To mount the second partition, as root:<placeholder-2/>Once you're done, to clean up:<placeholder-3/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:309(title)
msgid "Mount a raw image (with LVM)"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:310(para)
msgid "If your partitions are managed with LVM, use losetup and kpartx as in the previous example to expose the partitions to the host:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:317(para)
msgid "Next, you need to use the <placeholder-1/> command to identify the LVM volume groups and then <placeholder-2/> to expose the volumes as devices:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:327(para)
msgid "Clean up when you're done:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:334(title)
msgid "Mount a qcow2 image (without LVM)"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:335(para)
msgid "You need the <literal>nbd</literal> (network block device) kernel module loaded to mount qcow2 images. This will load it with support for 16 block devices, which is fine for our purposes. As root:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:340(para)
msgid "Assuming the first block device (<filename>/dev/nbd0</filename>) is not currently in use, we can expose the disk partitions using the <placeholder-1/> and <placeholder-2/> commands. As root:<placeholder-3/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:347(para)
msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created for each partition:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:356(para)
msgid "If the network block device you selected was already in use, the initial <placeholder-1/> command will fail silently, and the <filename>/dev/nbd3p{1,2,3}</filename> device files will not be created."
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:363(para)
msgid "If the image partitions are not managed with LVM, they can be mounted directly:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:367(para)
msgid "When you're done, clean up:"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:372(title)
msgid "Mount a qcow2 image (with LVM)"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:373(para)
msgid "If the image partitions are managed with LVM, after you use <placeholder-1/> and <placeholder-2/>, you must use <placeholder-3/> and <placeholder-4/> in order to expose the LVM partitions as devices that can be mounted:<placeholder-5/>"
msgstr ""

#: ./doc/image-guide/ch_modifying_images.xml:387(para)
msgid "When you're done, clean up:<placeholder-1/>"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:80(None) ./doc/image-guide/section_centos-example.xml:84(None)
msgid "@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:96(None)
msgid "@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:107(None)
msgid "@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:122(None)
msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:188(None)
msgid "@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:6(title)
msgid "Example: CentOS image"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:7(para)
msgid "We'll run through an example of installing a CentOS image. This will focus mainly on CentOS 6.4. Because the CentOS installation process may change across versions, if you are using a different version of CentOS the installer steps may differ."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:13(title)
msgid "Download a CentOS install ISO"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:17(para)
msgid "Navigate to the <link href=\"http://www.centos.org/modules/tinycontent/index.php?id=30\">CentOS mirrors</link> page."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:22(para)
msgid "Click one of the <literal>HTTP</literal> links in the right-hand column next to one of the mirrors."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:27(para)
msgid "Click the folder link of the CentOS version you want to use. For example, <literal>6.4/</literal>."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:32(para)
msgid "Click the <literal>isos/</literal> folder link."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:36(para)
msgid "Click the <literal>x86_64/</literal> folder link for 64-bit images."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:40(para)
msgid "Click the ISO image you want to download. The netinstall ISO. For example, <filename>CentOS-6.4-x86_64-netinstall.iso</filename> is a good choice since it's a smaller image that will download missing packages from the Internet during the install process."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:51(title) ./doc/image-guide/section_ubuntu-example.xml:21(title)
msgid "Start the install process"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:52(para) ./doc/image-guide/section_ubuntu-example.xml:22(para)
msgid "Start the installation process using either <placeholder-1/> or <placeholder-2/> as described in the previous section. If using <placeholder-3/>, don't forget to connect your VNC client to the virtual machine."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:58(para)
msgid "We will assume the name of your virtual machine image is <literal>centos-6.4</literal>, which we need to know when using <placeholder-1/> commands to manipulate the state of the image."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:62(para) ./doc/image-guide/section_ubuntu-example.xml:32(para)
msgid "If you're using virt-manager, the commands should look something like this:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:73(title) ./doc/image-guide/section_centos-example.xml:174(title) ./doc/image-guide/section_ubuntu-example.xml:43(title) ./doc/image-guide/section_ubuntu-example.xml:69(title)
msgid "Step through the install"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:74(para)
msgid "At the initial Installer boot menu, choose the \"Install or upgrade an existing system\" option. Step through the install prompts, the defaults should be fine."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:89(title)
msgid "Configure TCP/IP"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:90(para)
msgid "The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 support is enabled with DHCP, which is the default."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:102(title)
msgid "Point the installer to a CentOS web server"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:103(para)
msgid "Choose URL as the installation method."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:116(para)
msgid "Consider using other mirrors as an alternative to mirror.umd.edu."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:110(para)
msgid "Depending on the version of CentOS, the net installer requires that the user specify either a URL, or the web site and a CentOS directory that corresponds to one of the CentOS mirrors. If the installer asks for a single URL, an example of a valid URL would be: <literal>http://mirror.umd/centos/6/os/x86_64</literal>.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:126(para)
msgid "If the installer asks for web site name and CentOS directory separately, an example would be:"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:131(para)
msgid "Web site name: <literal>mirror.umd.edu</literal>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:136(para)
msgid "CentOS directory: <literal>centos/6/os/x86_64</literal>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:141(para)
msgid "See <link href=\"http://www.centos.org/modules/tinycontent/index.php?id=30\">CentOS mirror page</link> to get a full list of mirrors, click on the \"HTTP\" link of a mirror to retrieve the web site name of a mirror."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:148(title)
msgid "Storage devices"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:149(para)
msgid "If asked about what type of devices your installation involves, choose \"Basic Storage Devices\"."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:153(title) ./doc/image-guide/section_ubuntu-example.xml:55(title)
msgid "Hostname"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:154(para)
msgid "The installer may ask you to choose a hostname. The default (<literal>localhost.localdomain</literal>) is fine. We will install the cloud-init package later, which will set the hostname on boot when a new instance is provisioned using this image."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:161(title) ./doc/image-guide/section_ubuntu-example.xml:75(title)
msgid "Partition the disks"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:162(para) ./doc/image-guide/section_ubuntu-example.xml:76(para)
msgid "There are different options for partitioning the disks. The default installation will use LVM partitions, and will create three partitions (<filename>/boot</filename>, <filename>/</filename>, swap), and this will work fine. Alternatively, you may wish to create a single ext4 partition, mounted to \"<literal>/</literal>\", should also work fine."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:169(para) ./doc/image-guide/section_ubuntu-example.xml:83(para)
msgid "If unsure, we recommend you use the installer's default partition scheme, since there is no clear advantage to one scheme or another."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:175(para)
msgid "Step through the install, using the default options. The simplest thing to do is to choose the \"Basic Server\" install (may be called \"Server\" install on older versions of CentOS), which will install an SSH server."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:181(title) ./doc/image-guide/section_ubuntu-example.xml:120(title)
msgid "Detach the CD-ROM and reboot"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:182(para)
msgid "Once the install completes, you will see the screen \"Congratulations, your CentOS installation is complete\"."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:197(replaceable) ./doc/image-guide/section_centos-example.xml:374(replaceable) ./doc/image-guide/section_ubuntu-example.xml:144(replaceable) ./doc/image-guide/section_ubuntu-example.xml:238(replaceable)
msgid "vm-image"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:192(para) ./doc/image-guide/section_ubuntu-example.xml:139(para)
msgid "To eject a disk using <placeholder-1/>, libvirt requires that you attach an empty disk at the same target that the CDROM was previously attached, which should be <literal>hdc</literal>. You can confirm the appropriate target using the <placeholder-2/> command."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:212(para)
msgid "Run the following commands from the host to eject the disk and reboot using virsh, as root. If you are using virt-manager, the commands below will work, but you can also use the GUI to detach and reboot it by manually stopping and starting.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:221(para)
msgid "In theory, the <placeholder-1/> command can be used instead of using destroy and start commands. However, in our testing we were unable to reboot successfully using the <placeholder-2/> command."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:230(title) ./doc/image-guide/section_ubuntu-example.xml:176(title)
msgid "Log in to newly created image"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:231(para)
msgid "When you boot for the first time after install, it may ask you about authentication tools, you can just choose \"Exit\". Then, log in as root using the root password you specified."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:237(title)
msgid "Configure to fetch metadata"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:243(para)
msgid "Install a cloud-init RPM, which is a port of the Ubuntu <link href=\"https://launchpad.net/cloud-init\">cloud-init</link> package. This is the recommended approach."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:250(para)
msgid "Modify <filename>/etc/rc.local</filename> to fetch desired information from the metadata service, as described below."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:238(para)
msgid "An instance must perform several steps on start up by interacting with the metadata service. For example, retrieve ssh public key and execute user data script. There are several ways to implement this functionality, including:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:257(title)
msgid "Use cloud-init to fetch the public key"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:258(para)
msgid "The cloud-init package will automatically fetch the public key from the metadata server and place the key in an account. You can install cloud-init inside the CentOS guest by adding the EPEL repo:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:264(para) ./doc/image-guide/section_ubuntu-example.xml:201(para)
msgid "The account varies by distribution. On Ubuntu-based virtual machines, the account is called \"ubuntu\". On Fedora-based virtual machines, the account is called \"ec2-user\"."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:268(para)
msgid "You can change the name of the account used by cloud-init by editing the <filename>/etc/cloud/cloud.cfg</filename> file and adding a line with a different user. For example, to configure cloud-init to put the key in an account named <literal>admin</literal>, edit the configuration file so it has the line:"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:278(title)
msgid "Write a script to fetch the public key (if no cloud-init)"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:280(para)
msgid "If you are not able to install the cloud-init package in your image, to fetch the ssh public key and add it to the root account, edit the <filename>/etc/rc.local</filename> file and add the following lines before the line “<literal>touch /var/lock/subsys/local</literal>”"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:310(para)
msgid "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) with - (hyphen). Make sure it's http: not http; and authorized_keys not authorized-keys."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:316(para)
msgid "The above script only retrieves the ssh public key from the metadata server. It does not retrieve <emphasis role=\"italic\">user data</emphasis>, which is optional data that can be passed by the user when requesting a new instance. User data is often used for running a custom script when an instance comes up."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:323(para)
msgid "As the OpenStack metadata service is compatible with version 2009-04-04 of the Amazon EC2 metadata service, consult the Amazon EC2 documentation on <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Using Instance Metadata</link> for details on how to retrieve user data."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:332(title)
msgid "Disable the zeroconf route"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:333(para)
msgid "In order for the instance to access the metadata service, disable the default zeroconf route:"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:338(title)
msgid "Configure console"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:345(replaceable)
msgid "..."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:339(para)
msgid "In order for <placeholder-1/> to work properly on CentOS 6.x, guests you may need to add the following lines to <filename>/boot/grub/menu.lst</filename><placeholder-2/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:348(title) ./doc/image-guide/section_ubuntu-example.xml:214(title)
msgid "Shut down the instance"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:349(para) ./doc/image-guide/section_ubuntu-example.xml:215(para)
msgid "From inside the instance, as root:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:353(title) ./doc/image-guide/section_ubuntu-example.xml:219(title)
msgid "Clean up (remove MAC address details)"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:354(para)
msgid "The operating system records the MAC address of the virtual ethernet card in locations such as <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> and <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:363(para) ./doc/image-guide/section_ubuntu-example.xml:227(para)
msgid "There is a utility called <placeholder-1/>, that performs various cleanup tasks such as removing the MAC address references. It will clean up a virtual machine image in place:<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:370(title) ./doc/image-guide/section_ubuntu-example.xml:234(title)
msgid "Undefine the libvirt domain"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:371(para)
msgid "Now that the image is ready to be uploaded to the Image Service, you no longer need to have this virtual machine image managed by libvirt. Use the <placeholder-1/> command to inform libvirt.<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:379(title) ./doc/image-guide/section_ubuntu-example.xml:243(title)
msgid "Image is complete"
msgstr ""

#: ./doc/image-guide/section_centos-example.xml:380(para)
msgid "The underlying image file you created with <placeholder-1/>. For example, <filename>/tmp/centos-6.4.qcow2</filename> is now ready for uploading to the OpenStack Image Service."
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:10(title)
msgid "OpenStack Virtual Machine Image Guide"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:12(titleabbrev)
msgid "VM Image Guide"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:20(orgname) ./doc/image-guide/bk-imageguide.xml:25(holder)
msgid "OpenStack Foundation"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:24(year)
msgid "2013"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:27(releaseinfo)
msgid "current"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:28(productname)
msgid "OpenStack"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:32(remark)
msgid "Remaining licensing details are filled in by the template."
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:37(para)
msgid "This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack."
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:44(date)
msgid "2013-10-25"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:48(para)
msgid "Adds information about image formats, properties."
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:55(date)
msgid "2013-10-17"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:59(para)
msgid "Havana release."
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:65(date)
msgid "2013-06-04"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:69(para)
msgid "Updated title for consistency."
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:76(date)
msgid "2013-05-28"
msgstr ""

#: ./doc/image-guide/bk-imageguide.xml:80(para)
msgid "Initial release of this guide."
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:50(None)
msgid "@@image: 'figures/ubuntu-install.png'; md5=a1f2ab707b7bc3122e20e6e0e4580887"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:104(None)
msgid "@@image: 'figures/ubuntu-software-selection.png'; md5=423be828f701345f7d20551a39f24271"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:115(None)
msgid "@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc"
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:128(None)
msgid "@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:6(title)
msgid "Example: Ubuntu image"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:7(para)
msgid "We'll run through an example of installing an Ubuntu image. This will focus mainly on Ubuntu 12.04 (Precise Pangolin) server. Because the Ubuntu installation process may change across versions, if you are using a different version of Ubuntu the installer steps may differ."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:13(title)
msgid "Download an Ubuntu install ISO"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:14(para)
msgid "In this example, we'll use the network installation ISO, since it's a smaller image. The 64-bit 12.04 network installer ISO is at <link href=\"http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/mini.iso\">http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/mini.iso</link>"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:28(para)
msgid "We will assume the name of your virtual machine image is <literal>ubuntu-12.04</literal>, which we need to know when using <placeholder-1/> commands to manipulate the state of the image."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:44(para)
msgid "At the initial Installer boot menu, choose the \"Install\" option. Step through the install prompts, the defaults should be fine."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:56(para)
msgid "The installer may ask you to choose a hostname. The default (<literal>ubuntu</literal>) is fine. We will install the cloud-init package later, which will set the hostname on boot when a new instance is provisioned using this image."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:64(title)
msgid "Select a mirror"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:65(para)
msgid "The default mirror proposed by the installer should be fine."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:70(para)
msgid "Step through the install, using the default options. When prompted for a username, the default (<literal>ubuntu</literal>) is fine."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:88(title)
msgid "Automatic updates"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:89(para)
msgid "The Ubuntu installer will ask how you want to manage upgrades on your system. This option depends on your specific use case. If your virtual machine instances will be connected to the internet, we recommend \"Install security updates automatically\"."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:96(title)
msgid "Software selection: OpenSSH server"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:97(para)
msgid "Choose \"OpenSSH server\"so that you will be able to SSH into the virtual machine when it launches inside of an OpenStack cloud."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:109(title)
msgid "Install GRUB boot loader"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:110(para)
msgid "Select \"Yes\" when asked about installing the GRUB boot loader to the master boot record."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:121(para)
msgid "Select the defaults for all of the remaining options. When the installation is complete, you will be prompted to remove the CD-ROM."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:133(para)
msgid "When you hit \"Continue\" the virtual machine will shut down, even though it says it will reboot."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:160(para)
msgid "Run the following commands in the host as root to start up the machine again as paused, eject the disk and resume. If you are using virt-manager, you may use the GUI instead.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:167(para)
msgid "In the example above, we start the instance paused, eject the disk, and then unpause. In theory, we could have ejected the disk at the \"Installation complete\" screen. However, our testing indicates that the Ubuntu installer locks the drive so that it cannot be ejected at that point."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:177(para)
msgid "When you boot for the first time after install, it may ask you about authentication tools, you can just choose 'Exit'. Then, log in as root using the root password you specified."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:183(title)
msgid "Install cloud-init"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:184(para)
msgid "The <placeholder-1/> script starts on instance boot and will search for a metadata provider to fetch a public key from. The public key will be placed in the default user account for the image."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:188(para)
msgid "Install the <package>cloud-init</package> package:"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:190(para)
msgid "When building Ubuntu images <placeholder-1/> must be explicitly configured for the metadata source in use. The OpenStack metadata server emulates the EC2 metadata service used by images in Amazon EC2."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:195(para)
msgid "To set the metadata source to be used by the image run the <placeholder-1/> command against the <package>cloud-init</package> package. When prompted select the <literal>EC2</literal> data source: <placeholder-2/>"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:205(para)
msgid "You can change the name of the account used by cloud-init by editing the <filename>/etc/cloud/cloud.cfg</filename> file and adding a line with a different user. For example, to configure cloud-init to put the key in an account named \"admin\", edit the config file so it has the line:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:220(para)
msgid "The operating system records the MAC address of the virtual ethernet card in locations such as <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:235(para)
msgid "Now that the image is ready to be uploaded to the Image Service, we no longer need to have this virtual machine image managed by libvirt. Use the <placeholder-1/> command to inform libvirt<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/section_ubuntu-example.xml:244(para)
msgid "The underlying image file that you created with <placeholder-1/>, such as <filename>/tmp/precise.qcow2</filename>, is now ready for uploading to the OpenStack Image Service."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:6(title)
msgid "Introduction"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:7(para)
msgid "An OpenStack Compute cloud is not very useful unless you have virtual machine images (which some people call \"virtual appliances\"). This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:10(para)
msgid "To keep things brief, we'll sometimes use the term \"image\" instead of \"virtual machine image\"."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:12(para)
msgid "What is a virtual machine image?"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:13(para)
msgid "A virtual machine image is a single file which contains a virtual disk that has a bootable operating system installed on it."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:15(para)
msgid "Virtual machine images come in different formats, some of which are described below. In a later chapter, we'll describe how to convert between formats."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:19(term)
msgid "Raw"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:26(para)
msgid "We don't recommend creating raw images by dd'ing block device files, we discuss how to create raw images later."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:20(para)
msgid "The \"raw\" image format is the simplest one, and is natively supported by both KVM and Xen hypervisors. You can think of a raw image as being the bit-equivalent of a block device file, created as if somebody had copied, say, <filename>/dev/sda</filename> to a file using the <placeholder-1/> command. <placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:32(term) ./doc/image-guide/ch_converting.xml:26(td) ./doc/image-guide/ch_converting.xml:27(literal)
msgid "qcow2"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:37(para)
msgid "Using sparse representation, so the image size is smaller"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:40(para)
msgid "Support for snapshots"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:33(para)
msgid "The <link href=\"http://en.wikibooks.org/wiki/QEMU/Images\">qcow2</link> (QEMU copy-on-write version 2) format is commonly used with the KVM hypervisor. It has some additional features over the raw format, such as:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:43(para)
msgid "Because qcow2 is sparse, it's often faster to convert a raw image to qcow2 and upload it then to upload the raw file."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:47(para)
msgid "Because raw images don't support snapshots, OpenStack Compute will automatically convert raw image files to qcow2 as needed."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:53(term)
msgid "AMI/AKI/ARI"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:59(para)
msgid "AMI (Amazon Machine Image):"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:60(para)
msgid "This is a virtual machine image in raw format, as described above."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:64(para)
msgid "AKI (Amazon Kernel Image)"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:65(para)
msgid "A kernel file that the hypervisor will load initially to boot the image. For a Linux machine, this would be a <emphasis>vmlinuz</emphasis> file."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:72(para)
msgid "ARI (Amazon Ramdisk Image)"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:73(para)
msgid "An optional ramdisk file mounted at boot time. For a Linux machine, this would be an <emphasis>initrd</emphasis> file."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:54(para)
msgid "The <link href=\"http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html\">AMI/AKI/ARI </link>format was the initial image format supported by Amazon EC2. The image consists of three files:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:81(term)
msgid "UEC tarball"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:84(para)
msgid "Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud Infrastructure."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:82(para)
msgid "A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains an AMI file, AKI file, and ARI file.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:90(term)
msgid "VMDK"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:91(para)
msgid "VMWare's ESXi hypervisor uses the <link href=\"http://www.vmware.com/technical-resources/interfaces/vmdk.html\">VMDK</link> (Virtual Machine Disk) format for images."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:96(term)
msgid "VDI"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:97(para)
msgid "VirtualBox uses the <link href=\"https://forums.virtualbox.org/viewtopic.php?t=8046\">VDI</link> (Virtual Disk Image) format for image files. None of the OpenStack Compute hypervisors support VDI directly, so you will need to convert these files to a different format to use them with OpenStack."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:104(term)
msgid "VHD"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:105(para)
msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:108(term)
msgid "VHDX"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:109(para)
msgid "The version of Hyper-V that ships with Microsoft Server 2012 uses the newer <link href=\"http://technet.microsoft.com/en-us/library/hh831446.aspx\">VHDX</link> format, which has some additional features over VHD such as support for larger disk sizes and protection against data corruption during power failures."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:115(term)
msgid "OVF"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:116(para)
msgid "<link href=\"http://www.dmtf.org/standards/ovf\">OVF</link> (Open Virtualization Format) is a packaging format for virtual machines, defined by the Distributed Management Task Force (DMTF) standards group. An OVF package contains one or more image files, a .ovf XML metadata file that contains information about the virtual machine, and possibly other files as well."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:121(para)
msgid "An OVF package can be distributed in different ways. For example, it could be distributed as a set of discrete files, or as a tar archive file with an .ova (open virtual appliance/application) extension."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:124(para)
msgid "OpenStack Compute does not currently have support for OVF packages, so you will need to extract the image file(s) from an OVF package if you wish to use it with OpenStack."
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:129(term)
msgid "ISO"
msgstr ""

#: ./doc/image-guide/ch_introduction.xml:130(para)
msgid "The <link href=\"http://www.ecma-international.org/publications/standards/Ecma-119.htm\">ISO</link> format is a disk image formatted with the read-only ISO 9660 (also known as ECMA-119) filesystem commonly used for CDs and DVDs. While we don't normally think of ISO as a virtual machine image format, since ISOs contain bootable filesystems with an installed operating system, you can treat them the same as you treat other virtual machine image files."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:6(title)
msgid "Tool support for image creation"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:8(para)
msgid "There are several tools that are designed to automate image creation."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:11(title)
msgid "Oz"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:22(para)
msgid "As of this writing, there are no Oz packages for Ubuntu, so you will need to either install from source or build your own .deb file."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:12(para)
msgid "<link href=\"https://github.com/clalancette/oz/wiki\">Oz</link> is a command-line tool that automates the process of creating a virtual machine image file. Oz is a Python app that interacts with KVM to step through the process of installing a virtual machine. It uses a predefined set of kickstart (Red Hat-based systems) and preseed files (Debian-based systems) for operating systems that it supports, and it can also be used to create Microsoft Windows images. On Fedora, install Oz with yum:<placeholder-1/><placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:26(para)
msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on github at <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. Here's how you would create a CentOS 6.4 image with Oz."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:33(para)
msgid "Create a template file (we'll call it <filename>centos64.tdl</filename>) with the following contents. The only entry you will need to change is the <literal>&lt;rootpw&gt;</literal> contents.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:71(para)
msgid "This Oz template specifies where to download the Centos 6.4 install ISO. Oz will use the version information to identify which kickstart file to use. In this case, it will be <link href=\"https://github.com/clalancette/oz/blob/master/oz/auto/RHEL6.auto\">RHEL6.auto</link>. It adds EPEL as a repository and install the <literal>epel-release</literal>, <literal>cloud-utils</literal>, and <literal>cloud-init</literal> packages, as specified in the <literal>packages</literal> section of the file."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:82(para)
msgid "After Oz does the initial OS install using the kickstart file, it customizes the image by doing an update. It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the <literal>command</literal> section of the XML file."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:88(para)
msgid "To run this, do, as root:"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:91(para)
msgid "The <literal>-d3</literal> flag tells Oz to show status information as it runs."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:95(para)
msgid "The <literal>-u</literal> tells Oz to do the customization (install extra packages, run the commands) once it does the initial install."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:101(para)
msgid "The <literal>-x &lt;filename&gt;</literal> flag tells Oz what filename to use to write out a libvirt XML file (otherwise it will default to something like <filename>centos64Apr_03_2013-12:39:42</filename>."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:89(para)
msgid "<placeholder-1/><placeholder-2/>If you leave out the <literal>-u</literal> flag, or you want to edit the file to do additional customizations, you can use the <placeholder-3/> command, using the libvirt XML file that <placeholder-4/> creates. For example: <placeholder-5/> Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh into the instance and perform the customizations."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:119(title)
msgid "VMBuilder"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:120(para)
msgid "<link href=\"https://launchpad.net/vmbuilder\">VMBuilder</link> (Virtual Machine Builder) is a command-line tool that creates virtual machine images for different hypervisors. The version of VMBuilder that ships with Ubuntu can only create Ubuntu virtual machine guests. The version of VMBuilder that ships with Debian can create Ubuntu and Debian virtual machine guests."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:127(para)
msgid "The <link href=\"https://help.ubuntu.com/12.04/serverguide/jeos-and-vmbuilder.html\"><citetitle>Ubuntu Server Guide</citetitle></link> has documentation on how to use VMBuilder to create an Ubuntu image."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:134(title)
msgid "BoxGrinder"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:135(para)
msgid "<link href=\"http://boxgrinder.org/\">BoxGrinder</link>  is another tool for creating virtual machine images, which it calls appliances. BoxGrinder can create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is currently only supported on Fedora."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:144(title)
msgid "VeeWee"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:145(para)
msgid "<link href=\"https://github.com/jedi4ever/veewee\"> VeeWee</link> is often used to build <link href=\"http://vagrantup.com\">Vagrant</link> boxes, but it can also be used to build KVM images."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:151(title)
msgid "imagefactory"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:152(para)
msgid "<link href=\"http://imgfac.org/\">imagefactory</link> is a newer tool designed to automate the building, converting, and uploading images to different cloud providers. It uses Oz as its back-end and includes support for OpenStack-based clouds."
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:159(title)
msgid "SUSE Studio"
msgstr ""

#: ./doc/image-guide/ch_creating_images_automatically.xml:160(para)
msgid "<link href=\"http://susestudio.com\">SUSE Studio</link> is a web application for building and testing software applications in a web browser. It supports the creation of physical, virtual or cloud-based applications and includes support for building images for OpenStack based clouds using SUSE Linux Enterprise and openSUSE as distributions."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:10(title)
msgid "OpenStack Linux image requirements"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:12(para)
msgid "For a Linux-based image to have full functionality in an OpenStack Compute cloud, there are a few requirements. For some of these, you can fulfill the requirement by installing the <link href=\"https://cloudinit.readthedocs.org/en/latest/\"><package>cloud-init</package></link> package. Read this section before you create your own image to be sure that the image supports the OpenStack features that you plan to use."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:22(para)
msgid "Disk partitions and resize root partition on boot (<package>cloud-init</package>)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:26(para) ./doc/image-guide/ch_openstack_images.xml:234(title)
msgid "No hard-coded MAC address information"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:29(para)
msgid "SSH server running"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:32(para) ./doc/image-guide/ch_openstack_images.xml:278(title)
msgid "Disable firewall"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:35(para)
msgid "Access instance using ssh public key (<package>cloud-init</package>)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:39(para)
msgid "Process user data and other metadata (<package>cloud-init</package>)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:43(para)
msgid "Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux kernel version &lt; 3.0)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:49(title)
msgid "Disk partitions and resize root partition on boot (cloud-init)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:51(para)
msgid "When you create a Linux image, you must decide how to partition the disks. The choice of partition method can affect the resizing functionality, as described in the following sections."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:55(para)
msgid "The size of the disk in a virtual machine image is determined when you initially create the image. However, OpenStack lets you launch instances with different size drives by specifying different flavors. For example, if your image was created with a 5 GB disk, and you launch an instance with a flavor of <literal>m1.small</literal>. The resulting virtual machine instance has, by default, a primary disk size of 10 GB. When the disk for an instance is resized up, zeros are just added to the end."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:65(para)
msgid "Your image must be able to resize its partitions on boot to match the size requested by the user. Otherwise, after the instance boots, you must manually resize the partitions to access the additional storage to which you have access when the disk size associated with the flavor exceeds the disk size with which your image was created."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:73(title)
msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:75(para)
msgid "If you use the OpenStack XenAPI driver, the Compute service automatically adjusts the partition and file system for your instance on boot. Automatic resize occurs if the following conditions are all true:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:82(para)
msgid "<literal>auto_disk_config=True</literal> is set as a property on the image in the image registry."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:87(para)
msgid "The disk on the image has only one partition."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:91(para)
msgid "The file system on the one partition is ext3 or ext4."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:95(para)
msgid "Therefore, if you use Xen, we recommend that when you create your images, you create a single ext3 or ext4 partition (not managed by LVM). Otherwise, read on."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:101(title)
msgid "Non-Xen with cloud-init/cloud-tools: One ext3/ext4 partition (no LVM, no /boot, no swap)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:103(para)
msgid "You must configure these items for your image:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:107(para)
msgid "The partition table for the image describes the original size of the image"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:111(para)
msgid "The file system for the image fills the original size of the image"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:115(para)
msgid "Then, during the boot process, you must:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:118(para)
msgid "Modify the partition table to make it aware of the additional space:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:122(para)
msgid "If you do not use LVM, you must modify the table to extend the existing root partition to encompass this additional space."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:128(para)
msgid "If you use LVM, you can add a new LVM entry to the partition table, create a new LVM physical volume, add it to the volume group, and extend the logical partition with the root volume."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:138(para)
msgid "Resize the root volume file system."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:141(para)
msgid "The simplest way to support this in your image is to install the <link href=\"https://launchpad.net/cloud-utils\">cloud-utils</link> package (contains the <placeholder-1/> tool for extending partitions), the <link href=\"https://launchpad.net/cloud-initramfs-tools\">cloud-initramfs-tools</link> package (which supports resizing root partition on the first boot), and the <link href=\"https://launchpad.net/cloud-init\"><package>cloud-init</package></link> package into your image. With these installed, the image performs the root partition resize on boot. For example, in the <filename>/etc/rc.local</filename> file. These packages are in the Ubuntu and Debian package repository, as well as the EPEL repository (for Fedora/RHEL/CentOS/Scientific Linux guests)."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:160(para)
msgid "If you cannot install <literal>cloud-initramfs-tools</literal>, Robert Plestenjak has a github project called <link href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-resize</link> that contains scripts that update a ramdisk by using <placeholder-1/> so that the image resizes properly on boot."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:168(para)
msgid "If you can install the cloud-utils and <package>cloud-init</package> packages, we recommend that when you create your images, you create a single ext3 or ext4 partition (not managed by LVM)."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:175(title)
msgid "Non-Xen without <package>cloud-init</package>/<package>cloud-tools</package>: LVM"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:178(para)
msgid "If you cannot install <package>cloud-init</package> and <package>cloud-tools</package> inside of your guest, and you want to support resize, you must write a script that your image runs on boot to modify the partition table. In this case, we recommend using LVM to manage your partitions. Due to a limitation in the Linux kernel (as of this writing), you cannot modify a partition table of a raw disk that has partitions currently mounted, but you can do this for LVM."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:189(para)
msgid "Detect if any additional space is available on the disk. For example, parse the output of <placeholder-1/>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:196(para)
msgid "Create a new LVM partition with the additional space. For example, <placeholder-1/>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:204(replaceable) ./doc/image-guide/ch_openstack_images.xml:211(replaceable) ./doc/image-guide/ch_openstack_images.xml:218(replaceable)
msgid "sda6"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:202(para)
msgid "Create a new physical volume. For example, <placeholder-1/>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:210(replaceable)
msgid "vg00"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:207(para)
msgid "Extend the volume group with this physical partition. For example, <placeholder-1/>.)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:217(replaceable) ./doc/image-guide/ch_openstack_images.xml:223(replaceable)
msgid "node-root"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:214(para)
msgid "Extend the logical volume contained the root partition by the amount of space. For example, <placeholder-1/>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:221(para)
msgid "Resize the root file system. For example, <placeholder-1/>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:187(para)
msgid "Your script must do something like the following:<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:226(para)
msgid "You do not need a <filename>/boot</filename> partition unless your image is an older Linux distribution that requires that <filename>/boot</filename> is not managed by LVM."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:235(para)
msgid "You must remove the network persistence rules in the image because they cause the network interface in the instance to come up as an interface other than eth0. This is because your image has a record of the MAC address of the network interface card when it was first installed, and this MAC address is different each time that the instance boots. You should alter the following files:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:245(para)
msgid "Replace <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> with an empty file (contains network persistence rules, including MAC address)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:251(para)
msgid "Replace <filename>/lib/udev/rules.d/75-persistent-net-generator.rules</filename> with an empty file (this generates the file above)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:257(para)
msgid "Remove the HWADDR line from <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> on Fedora-based images"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:263(para)
msgid "If you delete the network persistent rules files, you may get a udev kernel warning at boot time, which is why we recommend replacing them with empty files instead."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:270(title)
msgid "Ensure ssh server runs"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:271(para)
msgid "You must install an ssh server into the image and ensure that it starts up on boot, or you cannot connect to your instance by using ssh when it boots inside of OpenStack. This package is typically called <literal>openssh-server</literal>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:279(para)
msgid "In general, we recommend that you disable any firewalls inside of your image and use OpenStack security groups to restrict access to instances. The reason is that having a firewall installed on your instance can make it more difficult to troubleshoot networking issues if you cannot connect to your instance."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:287(title)
msgid "Access instance by using ssh public key (cloud-init)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:289(para)
msgid "The typical way that users access virtual machines running on OpenStack is to ssh using public key authentication. For this to work, your virtual machine image must be configured to download the ssh public key from the OpenStack metadata service or config drive, at boot time."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:296(title)
msgid "Use <package>cloud-init</package> to fetch the public key"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:298(para)
msgid "The <package>cloud-init</package> package automatically fetches the public key from the metadata server and places the key in an account. The account varies by distribution. On Ubuntu-based virtual machines, the account is called <literal>ubuntu</literal>. On Fedora-based virtual machines, the account is called <literal>ec2-user</literal>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:306(para)
msgid "You can change the name of the account used by <package>cloud-init</package> by editing the <filename>/etc/cloud/cloud.cfg</filename> file and adding a line with a different user. For example, to configure <package>cloud-init</package> to put the key in an account named <literal>admin</literal>, edit the configuration file so it has the line:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:316(title)
msgid "Write a custom script to fetch the public key"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:318(para)
msgid "If you are unable or unwilling to install <package>cloud-init</package> inside the guest, you can write a custom script to fetch the public key and add it to a user account."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:322(para)
msgid "To fetch the ssh public key and add it to the root account, edit the <filename>/etc/rc.local</filename> file and add the following lines before the line “touch /var/lock/subsys/local”. This code fragment is taken from the <link href=\"https://github.com/rackerjoe/oz-image-build/blob/master/templates/centos60_x86_64.tdl\">rackerjoe oz-image-build CentOS 6 template</link>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:362(para)
msgid "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) with - (hyphen). If editing a file over a VNC session, make sure it's http: not http; and authorized_keys not authorized-keys."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:374(title)
msgid "Process user data and other metadata (cloud-init)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:376(para)
msgid "In addition to the ssh public key, an image might need additional information from OpenStack, such as <link href=\"http://docs.openstack.org/user-guide/content/user-data.html\">user data</link> that the user submitted when requesting the image. For example, you might want to set the host name of the instance when it is booted. Or, you might wish to configure your image so that it executes user data content as a script on boot."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:384(para)
msgid "This information is accessible through the metadata service or the <link href=\"http://docs.openstack.org/user-guide/content/config-drive.html\">config drive</link>. As the OpenStack metadata service is compatible with version 2009-04-04 of the Amazon EC2 metadata service, consult the Amazon EC2 documentation on <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Using Instance Metadata</link> for details on how to retrieve user data."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:395(para)
msgid "The easiest way to support this type of functionality is to install the <package>cloud-init</package> package into your image, which is configured by default to treat user data as an executable script, and sets the host name."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:402(title)
msgid "Ensure image writes boot log to console"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:403(para)
msgid "You must configure the image so that the kernel writes the boot log to the <literal>ttyS0</literal> device. In particular, the <literal>console=ttyS0</literal> argument must be passed to the kernel on boot."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:407(para)
msgid "If your image uses grub2 as the boot loader, there should be a line in the grub configuration file. For example, <filename>/boot/grub/grub.cfg</filename>, which looks something like this:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:412(para)
msgid "If <literal>console=ttyS0</literal> does not appear, you must modify your grub configuration. In general, you should not update the <filename>grub.cfg</filename> directly, since it is automatically generated. Instead, you should edit <filename>/etc/default/grub</filename> and modify the value of the <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> variable: <placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:421(para)
msgid "Next, update the grub configuration. On Debian-based operating-systems such as Ubuntu, run this command:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:424(para)
msgid "On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this command:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:429(title)
msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:431(para)
msgid "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel did not have support paravirtualized Xen virtual machine instances (what Xen calls DomU guests). If you are running the Xen hypervisor with paravirtualization, and you want to create an image for an older Linux distribution that has a pre 3.0 kernel, you must ensure that the image boots a kernel that has been compiled with Xen support."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:441(title)
msgid "Manage the image cache"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:442(para)
msgid "Use options in <filename>nova.conf</filename> to control whether, and for how long, unused base images are stored in <filename>/var/lib/nova/instances/_base/</filename>. If you have configured live migration of instances, all your compute nodes share one common <filename>/var/lib/nova/instances/</filename> directory."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:449(para)
msgid "For information about libvirt images in OpenStack, see <link href=\"http://www.pixelbeat.org/docs/openstack_libvirt_images/\">The life of an OpenStack libvirt image from Pádraig Brady</link>."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:455(caption)
msgid "Image cache management configuration options"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:461(td)
msgid "Configuration option=Default value"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:462(td)
msgid "(Type) Description"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:467(td)
msgid "preallocate_images=none"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:468(para)
msgid "(StrOpt) VM image preallocation mode:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:471(para)
msgid "<literal>none</literal>. No storage provisioning occurs up front."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:476(para)
msgid "<literal>space</literal>. Storage is fully allocated at instance start. The <literal>$instance_dir/</literal> images are <link 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."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:493(td)
msgid "remove_unused_base_images=True"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:494(td)
msgid "(BoolOpt) Should unused base images be removed? When set to True, the interval at which base images are removed are set with the following two settings. If set to False base images are never removed by Compute."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:501(td)
msgid "remove_unused_original_minimum_age_seconds=86400"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:502(td)
msgid "(IntOpt) Unused unresized base images younger than this are not removed. Default is 86400 seconds, or 24 hours."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:507(td)
msgid "remove_unused_resized_minimum_age_seconds=3600"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:508(td)
msgid "(IntOpt) Unused resized base images younger than this are not removed. Default is 3600 seconds, or one hour."
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:514(para)
msgid "To see how the settings affect the deletion of a running instance, check the directory where the images are stored:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:518(para)
msgid "In the <filename>/var/log/compute/compute.log</filename> file, look for the identifier:"
msgstr ""

#: ./doc/image-guide/ch_openstack_images.xml:525(para)
msgid "Because 86400 seconds (24 hours) is the default time for <literal>remove_unused_original_minimum_age_seconds</literal>, you can either wait for that time interval to see the base image removed, or set the value to a shorter time period in <filename>nova.conf</filename>. Restart all nova services after changing a setting in <filename>nova.conf</filename>."
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:8(title)
msgid "Example: Microsoft Windows image"
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:9(para)
msgid "We do not yet have a fully documented example of how to create a Microsoft Windows image. You can use libvirt to install Windows from an installation DVD using the same approach as with the CentOS and Ubuntu examples. Once the initial install is done, you will need to perform some Windows-specific customizations."
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:14(title)
msgid "Install VirtIO drivers"
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:15(para)
msgid "Installing the <link href=\"http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers\">VirtIO paravirtualizaion drivers for Windows</link> will improve virtual machine performance when using KVM as the hypervisor to run Windows."
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:20(title)
msgid "Sysprep"
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:21(para)
msgid "Microsoft has a special tool called <link href=\"http://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx\">Sysprep</link> that must be run inside of a Windows guest to prepare it for use as a virtual machine image. On Windows 2012 server, invoke sysprep, as follows: <placeholder-1/>"
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:28(title)
msgid "cloudbase-init"
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:29(para)
msgid "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> is a Windows port of cloud-init that should be installed inside of the guest. The <link href=\"https://github.com/cloudbase/cloudbase-init\">source code</link> is available on github."
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:35(title)
msgid "Jordan Rinke's OpenStack Windows resources"
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:36(para)
msgid "Jordan Rinke maintains <link href=\"https://github.com/jordanrinke/openstack\">a collection of resources</link> for managing OpenStack Windows virtual machine guests."
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:41(title)
msgid "Windows instances require the timezone to be \"localtime\""
msgstr ""

#: ./doc/image-guide/section_windows-example.xml:42(para)
msgid "When uploading Windows images, you must set the <literal>os_type</literal> parameter to <literal>windows</literal>, which causes instances to use the local time zone. Failing to set this will cause the clock timezone to be UTC, which has unexpected side effects in Windows."
msgstr ""

#: ./doc/image-guide/section_freebsd-example.xml:8(title)
msgid "Example: FreeBSD image"
msgstr ""

#: ./doc/image-guide/section_freebsd-example.xml:9(para)
msgid "We do not yet have a fully documented example of how to create a FreeBSD image."
msgstr ""

#: ./doc/image-guide/section_freebsd-example.xml:11(para)
msgid "See the <link href=\"http://pellaeon.github.io/bsd-cloudinit/\">bsd-cloudinit</link> project for information on how to build a FreeBSD VM image that works with OpenStack."
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/ch_creating_images_manually.xml:82(None)
msgid "@@image: 'figures/virt-manager-new.png'; md5=3528ebfc1b945b7dd80a34897b8fe98e"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:10(title)
msgid "Create images manually"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:11(para)
msgid "Creating a new image is a step done outside of your OpenStack installation. You create the new image manually on your own system and then upload the image to your cloud."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:15(para)
msgid "To create a new image, you will need the installation CD or DVD ISO file for the guest operating system. You'll also need access to a virtualization tool. You can use KVM for this. Or, if you have a GUI desktop virtualization tool (such as, VMWare Fusion and VirtualBox), you can use that instead and just convert the file to raw once you're done."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:21(para)
msgid "When you create a new virtual machine image, you will need to connect to the graphical console of the hypervisor, which acts as the virtual machine's display and allows you to interact with the guest operating system's installer using your keyboard and mouse. KVM can expose the graphical console using the <link href=\"https://en.wikipedia.org/wiki/Virtual_Network_Computing\">VNC</link> (Virtual Network Computing) protocol or the newer <link href=\"http://spice-space.org\">SPICE</link> protocol. We'll use the VNC protocol here, since you're more likely to be able to find a VNC client that works on your local desktop."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:34(title)
msgid "Verify the libvirt default network is running"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:35(para)
msgid "Before starting a virtual machine with libvirt, verify that the libvirt \"default\" network has been started. This network must be active for your virtual machine to be able to connect out to the network. Starting this network will create a Linux bridge (usually called <literal>virbr0</literal>), iptables rules, and a dnsmasq process that will serve as a DHCP server."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:42(para)
msgid "To verify that the libvirt \"default\" network is enabled, use the <placeholder-1/> command and verify that the \"default\" network is active:"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:49(para)
msgid "If the network is not active, start it by doing:"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:53(title)
msgid "Use the virt-manager X11 GUI"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:54(para)
msgid "If you plan to create a virtual machine image on a machine that can run X11 applications, the simplest way to do so is to use the <placeholder-1/> GUI, which is installable as the <literal>virt-manager</literal> package on both Fedora-based and Debian-based systems. This GUI has an embedded VNC client in it that will let you view and interact with the guest's graphical console."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:62(para)
msgid "If you are building the image on a headless server, and you have an X server on your local machine, you can launch <placeholder-1/>  using ssh X11 forwarding to access the GUI. Since virt-manager interacts directly with libvirt, you typically need to be root to access it. If you can ssh directly in as root (or with a user that has permissions to interact with libvirt), do:<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:73(para)
msgid "The <literal>-X</literal> flag passed to ssh will enable X11 forwarding over ssh. If this does not work, try replacing it with the <literal>-Y</literal> flag."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:70(para)
msgid "If the account you use to ssh into your server does not have permissions to run libvirt, but has sudo privileges, do:<placeholder-1/><placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:78(para)
msgid "Click the \"New\" button at the top-left and step through the instructions. <placeholder-1/>You will be shown a series of dialog boxes that will allow you to specify information about the virtual machine."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:87(para)
msgid "When using qcow2 format images you should check the option 'customize before install', go to disk properties and explicitly select the qcow2 format. This ensures the virtual machine disk size will be correct."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:95(title)
msgid "Use virt-install and connect by using a local VNC client"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:97(para)
msgid "If you do not wish to use virt-manager (for example, you do not want to install the dependencies on your server, you don't have an X server running locally, the X11 forwarding over SSH isn't working), you can use the <placeholder-1/> tool to boot the virtual machine through libvirt and connect to the graphical console from a VNC client installed on your local machine."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:105(para)
msgid "Because VNC is a standard protocol, there are multiple clients available that implement the VNC spec, including <link href=\"http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Welcome_to_TigerVNC\">TigerVNC</link> (multiple platforms), <link href=\"http://tightvnc.com/\">TightVNC</link> (multiple platforms), <link href=\"http://realvnc.com/\">RealVNC</link> (multiple platforms), <link href=\"http://sourceforge.net/projects/chicken/\">Chicken</link> (Mac OS X), <link href=\"http://userbase.kde.org/Krdc\">Krde</link> (KDE), and <link href=\"http://projects.gnome.org/vinagre/\">Vinagre</link> (GNOME)."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:120(para)
msgid "The following example shows how to use the <placeholder-1/> command to create an empty image file <placeholder-2/> command to start up a virtual machine using that image file. As root:"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:154(para)
msgid "When using the libvirt <literal>default</literal> network, libvirt will connect the virtual machine's interface to a bridge called <literal>virbr0</literal>. There is a dnsmasq process managed by libvirt that will hand out an IP address on the 192.168.122.0/24 subnet, and libvirt has iptables rules for doing NAT for IP addresses on this subnet."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:137(para)
msgid "The KVM hypervisor starts the virtual machine with the libvirt name, <literal>centos-6.4</literal>, with 1024 MB of RAM. The virtual machine also has a virtual CD-ROM drive associated with the <filename>/data/CentOS-6.4-x86_64-netinstall.iso</filename> file and a local 10 GB hard disk in qcow2 format that is stored in the host at <filename>/data/centos-6.4.qcow2</filename>. It configures networking to use libvirt's default network. There is a VNC server that is listening on all interfaces, and libvirt will not attempt to launch a VNC client automatically nor try to display the text console (<literal>--no-autoconsole</literal>). Finally, libvirt will attempt to optimize the configuration for a Linux guest running a RHEL 6.x distribution.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:163(para)
msgid "Run the <placeholder-1/> command to see a range of allowed <literal>--os-variant</literal> options."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:167(replaceable)
msgid "vm-name"
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:166(para)
msgid "Use the <placeholder-1/> command to get the VNC port number."
msgstr ""

#: ./doc/image-guide/ch_creating_images_manually.xml:171(para)
msgid "In the example above, the guest <literal>centos-6.4</literal> uses VNC display <literal>:1</literal>, which corresponds to tcp port <literal>5901</literal>. You should be able to connect to a VNC client running on your local machine to display :1 on the remote machine and step through the installation process."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:6(title)
msgid "Disk and container formats for images"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:8(para)
msgid "When you add an image to the Image Service, you can specify its disk and container formats."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:11(title)
msgid "Disk formats"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:12(para)
msgid "The disk format of a virtual machine image is the format of the underlying disk image. Virtual appliance vendors have different formats for laying out the information contained in a virtual machine disk image."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:16(para)
msgid "Set the disk format for your image to one of the following values:"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:20(para)
msgid "<literal>raw</literal>. An unstructured disk image format; if you have a file without an extension it is possibly a raw format"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:25(para)
msgid "<literal>vhd</literal>. The VHD disk format, a common disk format used by virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:31(para)
msgid "<literal>vmdk</literal>. Common disk format supported by many common virtual machine monitors"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:36(para)
msgid "<literal>vdi</literal>. Supported by VirtualBox virtual machine monitor and the QEMU emulator"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:41(para)
msgid "<literal>iso</literal>. An archive format for the data contents of an optical disc, such as CD-ROM."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:46(para)
msgid "<literal>qcow2</literal>. Supported by the QEMU emulator that can expand dynamically and supports Copy on Write"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:51(para) ./doc/image-guide/section_glance_image-formats.xml:87(para)
msgid "<literal>aki</literal>. An Amazon kernel image."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:55(para) ./doc/image-guide/section_glance_image-formats.xml:91(para)
msgid "<literal>ari</literal>. An Amazon ramdisk image."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:59(para) ./doc/image-guide/section_glance_image-formats.xml:95(para)
msgid "<literal>ami</literal>. An Amazon machine image."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:65(title)
msgid "Container formats"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:66(para)
msgid "The container format indicates whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:70(para)
msgid "The Image Service and other OpenStack projects do not currently support the container format. It is safe to specify <literal>bare</literal> as the container format if you are unsure."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:75(para)
msgid "You can set the container format for your image to one of the following values:"
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:79(para)
msgid "<literal>bare</literal>. The image does not have a container or metadata envelope."
msgstr ""

#: ./doc/image-guide/section_glance_image-formats.xml:83(para)
msgid "<literal>ovf</literal>. The OVF container format."
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:7(title)
msgid "Image metadata"
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:9(para)
msgid "Image metadata can help end users determine the nature of an image, and is used by associated OpenStack components and drivers which interface with the Image Service."
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:11(para)
msgid "Metadata can also determine the scheduling of hosts. If the <option>property</option> option is set on an image, and Compute is configured so that the <systemitem>ImagePropertiesFilter</systemitem> scheduler filter is enabled (default), then the scheduler only considers compute hosts that satisfy that property."
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:15(para)
msgid "Compute's <systemitem>ImagePropertiesFilter</systemitem> value is specified in the <option>scheduler_default_filter</option> value in the <filename>/etc/nova/nova.conf</filename> file."
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:18(para)
msgid "You can add metadata to Image Service images by using the <option>--property <replaceable>key</replaceable>=<replaceable>value</replaceable></option> option with the <placeholder-1/> or <placeholder-2/> command. More than one property can be specified. For example:"
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:22(replaceable)
msgid "img-uuid"
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:23(para)
msgid "Common image properties are also specified in the <filename>/etc/glance/schema-image.json</filename> file. For a complete list of valid property keys and values, refer to the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Reference</citetitle></link>."
msgstr ""

#: ./doc/image-guide/section_glance-image-metadata.xml:28(para)
msgid "All associated properties for an image can be displayed using the <placeholder-1/> command. For example:"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:4(title)
msgid "Converting between image formats"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:5(para)
msgid "Converting images from one format to another is generally straightforward."
msgstr ""

#: ./doc/image-guide/ch_converting.xml:7(title)
msgid "qemu-img convert: raw, qcow2, VDI, VMDK"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:8(para)
msgid "The <placeholder-1/> command can do conversion between multiple formats, including raw, qcow2, VDI (VirtualBox), VMDK (VMWare) and VHD (Hyper-V)."
msgstr ""

#: ./doc/image-guide/ch_converting.xml:12(caption)
msgid "qemu-img format strings"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:16(th)
msgid "Image format"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:17(th)
msgid "Argument to qemu-img"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:22(td) ./doc/image-guide/ch_converting.xml:23(literal)
msgid "raw"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:30(td)
msgid "VDI (VirtualBox)"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:31(literal)
msgid "vdi"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:34(td)
msgid "VMDK (VMWare)"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:35(literal)
msgid "vmdk"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:38(td)
msgid "VHD (Hyper-V)"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:39(literal)
msgid "vpc"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:43(para)
msgid "This example will convert a raw image file named centos63.dsk to a qcow2 image file."
msgstr ""

#: ./doc/image-guide/ch_converting.xml:47(para)
msgid "To convert from vmdk to raw, you would do: <placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:51(para)
msgid "The <literal>-f <replaceable>format</replaceable></literal> flag is optional. If omitted, qemu-img will try to infer the image format."
msgstr ""

#: ./doc/image-guide/ch_converting.xml:57(title)
msgid "VBoxManage: VDI (VirtualBox) to raw"
msgstr ""

#: ./doc/image-guide/ch_converting.xml:58(para)
msgid "If you've created a VDI image using VirtualBox, you can convert it to raw format using the <placeholder-1/> command-line tool that ships with VirtualBox. On Mac OS X, VirtualBox stores images by default in the <filename>~/VirtualBox VMs/</filename> directory. The following example creates a raw image in the current directory from a VirtualBox VDI image.<placeholder-2/>"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:6(title)
msgid "Get images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:8(para)
msgid "The simplest way to obtain a virtual machine image that works with OpenStack is to download one that someone else has already created."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:11(title)
msgid "CirrOS (test) images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:12(para)
msgid "CirrOS is a minimal Linux distribution that was designed for use as a test image on clouds such as OpenStack Compute. You can download a CirrOS image in various formats from the <link href=\"https://launchpad.net/cirros/+download\">CirrOS Launchpad download page</link>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:21(para)
msgid "In a CirrOS image, the login account is <literal>cirros</literal>. The password is <literal>cubswin:)</literal>"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:16(para)
msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is <link href=\"http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img\">cirros-0.3.2-x86_64-disk.img</link><placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:27(title)
msgid "Official Ubuntu images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:28(para)
msgid "Canonical maintains an <link href=\"http://cloud-images.ubuntu.com/\">official set of Ubuntu-based images</link>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:30(para)
msgid "Images are arranged by Ubuntu release, and by image release date, with \"current\" being the most recent. For example, the page that contains the most recently built image for Ubuntu 12.04 \"Precise Pangolin\" is <link href=\"http://cloud-images.ubuntu.com/precise/current/\">http://cloud-images.ubuntu.com/precise/current/</link>. Scroll to the bottom of the page for links to images that can be downloaded directly."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:40(para)
msgid "In an Ubuntu cloud image, the login account is <literal>ubuntu</literal>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:36(para)
msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent version of the 64-bit QCOW2 image for Ubuntu 12.04 is <link href=\"http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img\">precise-server-cloudimg-amd64-disk1.img</link>.<placeholder-1/>"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:45(title)
msgid "Official Red Hat Enterprise Linux images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:46(para)
msgid "Red Hat maintains an official Red Hat Enterprise Linux 6 cloud image. A valid Red Hat Enterprise Linux 6 subscription is required to download the <link href=\"https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=16952\">KVM Guest Image</link>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:53(para)
msgid "A <link href=\"https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=10486\">boot.iso</link> image is also available. This is the same as the <literal>boot.iso</literal> file provided on the Red Hat Enterprise Linux installation DVD. It is a minimal image suitable for kickstarting operating system installation over a network."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:63(title)
msgid "Official Fedora images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:64(para)
msgid "The Fedora project maintains a list of official cloud images at <link href=\"http://cloud.fedoraproject.org/\"/>. The images include the <systemitem class=\"process\">cloud-init</systemitem> utility to support key and user data injection. The default user name is <systemitem class=\"username\">fedora</systemitem>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:72(title)
msgid "Official openSUSE and SLES images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:73(para)
msgid "SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images for direct download. Instead, they provide a web-based tool called <link href=\"http://susestudio.com\">SUSE Studio</link> that you can use to build openSUSE and SLES images."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:79(para)
msgid "For example, Christian Berendt used <link href=\"http://www.opensuse.org\">openSUSE</link> to create <link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-12-3\"> a test openSUSE 12.3 image</link>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:84(title)
msgid "Official images from other Linux distributions"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:85(para)
msgid "As of this writing, we are not aware of other distributions that provide images for download."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:88(title)
msgid "Rackspace Cloud Builders (multiple distros) images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:90(para)
msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link>."
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:96(title)
msgid "Microsoft Windows images"
msgstr ""

#: ./doc/image-guide/ch_obtaining_images.xml:97(para)
msgid "Cloudbase Solutions hosts an <link href=\"http://www.cloudbase.it/ws2012/\">OpenStack Windows Server 2012 Standard Evaluation image</link> that runs on Hyper-V, KVM, and XenServer/XCP."
msgstr ""

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: ./doc/image-guide/ch_obtaining_images.xml:0(None)
msgid "translator-credits"
msgstr ""