# SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-2016, OpenStack contributors # This file is distributed under the same license as the Virtual Machine Image Guide package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Virtual Machine Image Guide 0.9\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-04-19 06:23+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../centos-image.rst:3 msgid "Example: CentOS image" msgstr "" #: ../centos-image.rst:5 msgid "" "This example shows you how to install a CentOS image and focuses mainly on " "CentOS 6.4. Because the CentOS installation process might differ across " "versions, the installation steps might differ if you use a different version " "of CentOS." msgstr "" #: ../centos-image.rst:11 msgid "Download a CentOS install ISO" msgstr "" #: ../centos-image.rst:13 msgid "" "Navigate to the `CentOS mirrors `_ " "page." msgstr "" #: ../centos-image.rst:15 msgid "" "Click one of the ``HTTP`` links in the right-hand column next to one of the " "mirrors." msgstr "" #: ../centos-image.rst:17 msgid "" "Click the folder link of the CentOS version that you want to use. For " "example, ``6.4/``." msgstr "" #: ../centos-image.rst:19 msgid "Click the ``isos/`` folder link." msgstr "" #: ../centos-image.rst:20 msgid "Click the ``x86_64/`` folder link for 64-bit images." msgstr "" #: ../centos-image.rst:21 msgid "" "Click the netinstall ISO image that you want to download. For example, " "``CentOS-6.4-x86_64-netinstall.iso`` is a good choice because it is a " "smaller image that downloads missing packages from the Internet during " "installation." msgstr "" #: ../centos-image.rst:27 msgid "Start the installation process" msgstr "" #: ../centos-image.rst:29 msgid "" "Start the installation process using either the :command:`virt-manager` or " "the :command:`virt-install` command as described in the previous section. If " "you use the :command:`virt-install` command, do not forget to connect your " "VNC client to the virtual machine." msgstr "" #: ../centos-image.rst:34 msgid "Assume that:" msgstr "" #: ../centos-image.rst:36 msgid "" "The name of your virtual machine image is ``centos-6.4``; you need this name " "when you use :command:`virsh` commands to manipulate the state of the image." msgstr "" #: ../centos-image.rst:39 msgid "You saved the netinstall ISO image to the ``/data/isos`` directory." msgstr "" #: ../centos-image.rst:41 msgid "" "If you use the :command:`virt-install` command, the commands should look " "something like this:" msgstr "" #: ../centos-image.rst:56 ../centos-image.rst:134 msgid "Step through the installation" msgstr "" #: ../centos-image.rst:58 msgid "" "At the initial Installer boot menu, choose the :guilabel:`Install or upgrade " "an existing system` option. Step through the installation prompts. Accept " "the defaults." msgstr "" #: ../centos-image.rst:66 msgid "Configure TCP/IP" msgstr "" #: ../centos-image.rst:68 msgid "" "The default TCP/IP settings are fine. In particular, ensure that ``Enable " "IPv4 support`` is enabled with DHCP, which is the default." msgstr "" #: ../centos-image.rst:76 msgid "Point the installer to a CentOS web server" msgstr "" #: ../centos-image.rst:78 msgid "Choose URL as the installation method." msgstr "" #: ../centos-image.rst:83 msgid "" "Depending on the version of CentOS, the net installer requires the user to " "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, a " "valid URL might be ``http://mirror.umd.edu/centos/6/os/x86_64``." msgstr "" #: ../centos-image.rst:91 msgid "Consider using other mirrors as an alternative to ``mirror.umd.edu``." msgstr "" #: ../centos-image.rst:96 msgid "" "If the installer asks for web site name and CentOS directory separately, you " "might enter:" msgstr "" #: ../centos-image.rst:99 msgid "Web site name: ``mirror.umd.edu``" msgstr "" #: ../centos-image.rst:100 msgid "CentOS directory: ``centos/6/os/x86_64``" msgstr "" #: ../centos-image.rst:102 msgid "" "See `CentOS mirror page `_ 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 "" #: ../centos-image.rst:107 msgid "Storage devices" msgstr "" #: ../centos-image.rst:109 msgid "" "If prompted about which type of devices your installation uses, choose :" "guilabel:`Basic Storage Devices`." msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:113 ../ubuntu-image.rst:52 msgid "Hostname" msgstr "" #: ../centos-image.rst:115 msgid "" "The installer may ask you to choose a host name. The default (``localhost." "localdomain``) is fine. You install the ``cloud-init`` package later, which " "sets the host name on boot when a new instance is provisioned using this " "image." msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:122 ../ubuntu-image.rst:71 msgid "Partition the disks" msgstr "" #: ../centos-image.rst:124 msgid "" "There are different options for partitioning the disks. The default " "installation uses LVM partitions, and creates three partitions (``/boot``, " "``/``, ``swap``), which works fine. Alternatively, you might want to create " "a single ext4 partition that is mounted to ``/``, which also works fine." msgstr "" #: ../centos-image.rst:130 msgid "" "If unsure, use the default partition scheme for the installer because no " "scheme is better than another." msgstr "" #: ../centos-image.rst:136 msgid "" "Step through the installation, 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 installs an SSH server." msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:142 ../ubuntu-image.rst:111 msgid "Detach the CD-ROM and reboot" msgstr "" #: ../centos-image.rst:144 msgid "" "When the installation has completed, the :guilabel:`Congratulations, your " "CentOS installation is complete` screen appears." msgstr "" #: ../centos-image.rst:151 msgid "" "To eject a disk by using the :command:`virsh` command, libvirt requires that " "you attach an empty disk at the same target that the CDROM was previously " "attached, which should be ``hdc``. You can confirm the appropriate target " "using the :command:`virsh dumpxml vm-image` command." msgstr "" #: ../centos-image.rst:172 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." msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:184 ../ubuntu-image.rst:164 msgid "Log in to newly created image" msgstr "" #: ../centos-image.rst:186 msgid "" "When you boot for the first time after installation, you might be prompted " "about authentication tools. Select :guilabel:`Exit`. Then, log in as root." msgstr "" #: ../centos-image.rst:191 msgid "Install the ACPI service" msgstr "" #: ../centos-image.rst:193 msgid "" "To enable the hypervisor to reboot or shutdown an instance, you must install " "and run the ``acpid`` service on the guest system." msgstr "" #: ../centos-image.rst:196 msgid "" "Run the following commands inside the CentOS guest to install the ACPI " "service and configure it to start when the system boots:" msgstr "" #: ../centos-image.rst:205 msgid "Configure to fetch metadata" msgstr "" #: ../centos-image.rst:207 msgid "" "An instance must interact with the metadata service to perform several tasks " "on start up. For example, the instance must get the ssh public key and run " "the user data script. To ensure that the instance performs these tasks, use " "one of these methods:" msgstr "" #: ../centos-image.rst:212 msgid "" "Install a ``cloud-init`` RPM, which is a port of the Ubuntu `cloud-init " "`_ package. This is the recommended " "approach." msgstr "" #: ../centos-image.rst:215 msgid "" "Modify the ``/etc/rc.local`` file to fetch desired information from the " "metadata service, as described in the next section." msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# openstack-images.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:219 ../openstack-images.rst:194 msgid "Use cloud-init to fetch the public key" msgstr "" #: ../centos-image.rst:221 msgid "" "The ``cloud-init`` package automatically fetches the public key from the " "metadata server and places the key in an account. You can install ``cloud-" "init`` inside the CentOS guest by adding the EPEL repo:" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:231 ../ubuntu-image.rst:196 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 "" #: ../centos-image.rst:235 msgid "" "You can change the name of the account used by ``cloud-init`` by editing the " "``/etc/cloud/cloud.cfg`` file and adding a line with a different user. For " "example, to configure ``cloud-init`` to put the key in an account named " "``admin``, add this line to the configuration file:" msgstr "" #: ../centos-image.rst:246 msgid "Write a script to fetch the public key (if no cloud-init)" msgstr "" #: ../centos-image.rst:248 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 ``/etc/rc." "d/rc.local`` file and add the following lines before the line ``touch /var/" "lock/subsys/local``:" msgstr "" #: ../centos-image.rst:282 msgid "" "Some VNC clients replace the colon (``:``) with a semicolon (``;``) and the " "underscore (``_``) with a hyphen (``-``). Make sure to specify ``http:`` and " "not ``http;``. Make sure to specify ``authorized_keys`` and not ``authorized-" "keys``." msgstr "" #: ../centos-image.rst:289 msgid "" "The previous script only gets the ssh public key from the metadata server. " "It does not get user data, which is optional data that can be passed by the " "user whenrequesting a new instance. User data is often used to run a custom " "script when an instance boots." msgstr "" #: ../centos-image.rst:294 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 " "`Using Instance Metadata `_ for details " "on how to get user data." msgstr "" #: ../centos-image.rst:301 msgid "Disable the zeroconf route" msgstr "" #: ../centos-image.rst:303 msgid "" "For the instance to access the metadata service, you must disable the " "default zeroconf route:" msgstr "" #: ../centos-image.rst:311 msgid "Configure console" msgstr "" #: ../centos-image.rst:313 msgid "" "For the :command:`nova console-log` command to work properly on CentOS 6." "``x``, you might need to add the following lines to the ``/boot/grub/menu." "lst`` file:" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:325 ../ubuntu-image.rst:210 msgid "Shut down the instance" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:327 ../ubuntu-image.rst:212 msgid "From inside the instance, as root:" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:334 ../ubuntu-image.rst:219 msgid "Clean up (remove MAC address details)" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# fedora-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:336 ../fedora-image.rst:196 msgid "" "The operating system records the MAC address of the virtual Ethernet card in " "locations such as ``/etc/sysconfig/network-scripts/ifcfg-eth0`` and ``/etc/" "udev/rules.d/70-persistent-net.rules`` 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 "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:343 ../ubuntu-image.rst:227 msgid "" "There is a utility called :command:`virt-sysprep`, that performs various " "cleanup tasks such as removing the MAC address references. It will clean up " "a virtual machine image in place:" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:352 ../ubuntu-image.rst:236 msgid "Undefine the libvirt domain" msgstr "" #: ../centos-image.rst:354 msgid "" "Now that you can upload the image to the Image service, you no longer need " "to have this virtual machine image managed by libvirt. Use the :command:" "`virsh undefine vm-image` command to inform libvirt:" msgstr "" # #-#-#-#-# centos-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# ubuntu-image.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../centos-image.rst:363 ../ubuntu-image.rst:247 msgid "Image is complete" msgstr "" #: ../centos-image.rst:365 msgid "" "The underlying image file that you created with the :command:`qemu-img " "create` command is ready to be uploaded. For example, you can upload the ``/" "tmp/centos-6.4.qcow2`` image to the Image service." msgstr "" #: ../convert-images.rst:0 msgid "qemu-img format strings" msgstr "" #: ../convert-images.rst:3 msgid "Converting between image formats" msgstr "" #: ../convert-images.rst:5 msgid "" "Converting images from one format to another is generally straightforward." msgstr "" #: ../convert-images.rst:8 msgid "qemu-img convert: raw, qcow2, qed, vdi, vmdk, vhd" msgstr "" #: ../convert-images.rst:10 msgid "" "The :command:`qemu-img convert` command can do conversion between multiple " "formats, including ``qcow2``, ``qed``, ``raw``, ``vdi``, ``vhd``, and " "``vmdk``." msgstr "" #: ../convert-images.rst:17 msgid "Image format" msgstr "" #: ../convert-images.rst:18 msgid "Argument to qemu-img" msgstr "" #: ../convert-images.rst:19 msgid "QCOW2 (KVM, Xen)" msgstr "" #: ../convert-images.rst:20 msgid "``qcow2``" msgstr "" #: ../convert-images.rst:21 msgid "QED (KVM)" msgstr "" #: ../convert-images.rst:22 msgid "``qed``" msgstr "" # #-#-#-#-# convert-images.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# # #-#-#-#-# image-formats.pot (Virtual Machine Image Guide 0.9) #-#-#-#-# #: ../convert-images.rst:23 ../image-formats.rst:31 msgid "raw" msgstr "" #: ../convert-images.rst:24 msgid "``raw``" msgstr "" #: ../convert-images.rst:25 msgid "VDI (VirtualBox)" msgstr "" #: ../convert-images.rst:26 msgid "``vdi``" msgstr "" #: ../convert-images.rst:27 msgid "VHD (Hyper-V)" msgstr "" #: ../convert-images.rst:28 msgid "``vpc``" msgstr "" #: ../convert-images.rst:29 msgid "VMDK (VMware)" msgstr "" #: ../convert-images.rst:30 msgid "``vmdk``" msgstr "" #: ../convert-images.rst:32 msgid "" "This example will convert a raw image file named ``image.img`` to a qcow2 " "image file." msgstr "" #: ../convert-images.rst:39 msgid "" "Run the following command to convert a vmdk image file to a raw image file." msgstr "" #: ../convert-images.rst:45 msgid "" "Run the following command to convert a vmdk image file to a qcow2 image file." msgstr "" #: ../convert-images.rst:53 msgid "" "The ``-f format`` flag is optional. If omitted, ``qemu-img`` will try to " "infer the image format." msgstr "" #: ../convert-images.rst:56 msgid "" "When converting an image file with Windows, ensure the virtio driver is " "installed. Otherwise, you will get a blue screen when launching the image " "due to lack of the virtio driver. Another option is to set the image " "properties as below when you update the image in the Image service to avoid " "this issue, but it will reduce performance significantly." msgstr "" #: ../convert-images.rst:69 msgid "VBoxManage: VDI (VirtualBox) to raw" msgstr "" #: ../convert-images.rst:71 msgid "" "If you've created a VDI image using VirtualBox, you can convert it to raw " "format using the ``VBoxManage`` command-line tool that ships with " "VirtualBox. On Mac OS X, and Linux, VirtualBox stores images by default in " "the ``~/VirtualBox VMs/`` directory. The following example creates a raw " "image in the current directory from a VirtualBox VDI image." msgstr "" #: ../create-images-automatically.rst:3 msgid "Tool support for image creation" msgstr "" #: ../create-images-automatically.rst:5 msgid "There are several tools that are designed to automate image creation." msgstr "" #: ../create-images-automatically.rst:8 msgid "Diskimage-builder" msgstr "" #: ../create-images-automatically.rst:10 msgid "" "`Diskimage-builder `_ is an automated disk image creation tool that supports a variety of " "distributions and architectures. Diskimage-builder (DIB) can build images " "for Fedora, Red Hat Enterprise Linux, Ubuntu, Debian, CentOS, and openSUSE. " "DIB is organized in a series of elements that build on top of each other to " "create specific images." msgstr "" #: ../create-images-automatically.rst:18 #: ../create-images-automatically.rst:207 msgid "To build an image, call the following script:" msgstr "" #: ../create-images-automatically.rst:24 msgid "" "This example creates a generic, bootable Ubuntu image of the latest release." msgstr "" #: ../create-images-automatically.rst:26 msgid "" "Further customization could be accomplished by setting environment variables " "or adding elements to the command-line:" msgstr "" #: ../create-images-automatically.rst:33 msgid "" "This example creates the image as before, but for arm architecture. More " "elements are available in the `git source directory `_ and documented in the " "`diskimage-builder elements documentation `_." msgstr "" #: ../create-images-automatically.rst:40 msgid "Oz" msgstr "" #: ../create-images-automatically.rst:42 msgid "" "`Oz `_ 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:" msgstr "" #: ../create-images-automatically.rst:57 msgid "" "As of this writing, there are no Oz packages for Ubuntu, so you will need to " "either install from the source or build your own .deb file." msgstr "" #: ../create-images-automatically.rst:60 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 `rackerjoe/oz-image-build/templates `_. Here's how you would create a " "CentOS 6.4 image with Oz." msgstr "" #: ../create-images-automatically.rst:66 msgid "" "Create a template file (we'll call it ``centos64.tdl``) with the following " "contents. The only entry you will need to change is the ```` " "contents." msgstr "" #: ../create-images-automatically.rst:106 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 `RHEL6.auto `_. It adds EPEL as a repository and install the " "``epel-release``, ``cloud-utils``, and ``cloud-init`` packages, as specified " "in the ``packages`` section of the file." msgstr "" #: ../create-images-automatically.rst:114 msgid "" "After Oz completes the initial OS install using the kickstart file, it " "customizes the image with an update. It also removes any reference to the " "eth0 device that libvirt creates while Oz does the customizing, as specified " "in the ``command`` section of the XML file." msgstr "" #: ../create-images-automatically.rst:119 msgid "To run this:" msgstr "" #: ../create-images-automatically.rst:125 msgid "The ``-d3`` flag tells Oz to show status information as it runs." msgstr "" #: ../create-images-automatically.rst:126 msgid "" "The ``-u`` tells Oz to do the customization (install extra packages, run the " "commands) once it does the initial install." msgstr "" #: ../create-images-automatically.rst:128 msgid "" "The ``-x`` flag tells Oz what filename to use to write out a libvirt XML " "file (otherwise it will default to something like " "``centos64Apr_03_2013-12:39:42``)." msgstr "" #: ../create-images-automatically.rst:132 msgid "" "If you leave out the ``-u`` flag, or you want to edit the file to do " "additional customizations, you can use the :command:`oz-customize` command, " "using the libvirt XML file that :command:`oz-install` creates. For example:" msgstr "" #: ../create-images-automatically.rst:141 msgid "" "Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh " "into the instance and perform the customizations." msgstr "" #: ../create-images-automatically.rst:145 msgid "VMBuilder" msgstr "" #: ../create-images-automatically.rst:147 msgid "" "`VMBuilder `_ (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 "" #: ../create-images-automatically.rst:154 msgid "" "The `Ubuntu Server Guide `_ has documentation on how to use VMBuilder to create an " "Ubuntu image." msgstr "" #: ../create-images-automatically.rst:159 msgid "VeeWee" msgstr "" #: ../create-images-automatically.rst:161 msgid "" "`VeeWee `_ is often used to build " "`Vagrant `_ boxes, but it can also be used to build " "the KVM images." msgstr "" #: ../create-images-automatically.rst:166 msgid "Packer" msgstr "" #: ../create-images-automatically.rst:168 msgid "" "`Packer `_ is a tool for creating machine images for " "multiple platforms from a single source configuration." msgstr "" #: ../create-images-automatically.rst:172 msgid "imagefactory" msgstr "" #: ../create-images-automatically.rst:174 msgid "" "`imagefactory `_ 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 "" #: ../create-images-automatically.rst:180 msgid "KIWI" msgstr "" #: ../create-images-automatically.rst:182 msgid "" "The `KIWI OS image builder `_ provides an " "operating system image builder for various Linux supported hardware " "platforms as well as for virtualization and cloud systems. It allows " "building of images based on openSUSE, SUSE Linux Enterprise, and Red Hat " "Enterprise Linux. The `openSUSE Documentation `_ explains how to use KIWI." msgstr "" #: ../create-images-automatically.rst:190 msgid "SUSE Studio" msgstr "" #: ../create-images-automatically.rst:192 msgid "" "`SUSE Studio `_ 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 "" #: ../create-images-automatically.rst:199 msgid "virt-builder" msgstr "" #: ../create-images-automatically.rst:201 msgid "" "`Virt-builder `_ is a tool for " "quickly building new virtual machines. You can build a variety of VMs for " "local or cloud use, usually within a few minutes or less. Virt-builder also " "has many ways to customize these VMs. Everything is run from the command " "line and nothing requires root privileges, so automation and scripting is " "simple." msgstr "" #: ../create-images-automatically.rst:214 msgid "To list the operating systems available to install:" msgstr "" #: ../create-images-automatically.rst:220 msgid "To import it into libvirt with :command:`virsh`:" msgstr "" #: ../create-images-manually.rst:3 msgid "Create images manually" msgstr "" #: ../create-images-manually.rst:17 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 "" #: ../create-images-manually.rst:21 msgid "" "To create a new image, you will need the installation CD or DVD ISO file for " "the guest operating system. You will 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 or VirtualBox), you can use that instead. " "Convert the file to raw once you are done." msgstr "" #: ../create-images-manually.rst:28 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 `VNC `_ (Virtual Network Computing) protocol or the " "newer `SPICE `_ protocol. We will use the VNC " "protocol here, since you are more likely to find a VNC client that works on " "your local desktop." msgstr "" #: ../create-images-manually.rst:39 msgid "" "To create an image for the Database service, see `Building Guest Images for " "OpenStack Trove `_." msgstr "" #: ../fedora-image.rst:3 msgid "Example: Fedora image" msgstr "" #: ../fedora-image.rst:5 msgid "" "Download a `Fedora `_ ISO image. This procedure lets " "you create a Fedora 20 image." msgstr "" #: ../fedora-image.rst:8 msgid "Start the installation using :command:`virt-install` as shown below:" msgstr "" #: ../fedora-image.rst:20 msgid "This will launch a VM and start the installation process." msgstr "" #: ../fedora-image.rst:44 msgid "Choose the VNC or text mode to set the installation options." msgstr "" #: ../fedora-image.rst:59 msgid "" "Set the timezone, network configuration, installation source, and the root " "password. Optionally, you can choose to create a user." msgstr "" #: ../fedora-image.rst:62 msgid "Set up the installation destination as shown below:" msgstr "" #: ../fedora-image.rst:125 msgid "" "Run the following commands from the host to eject the disk and reboot using " "the :command:`virsh` command, as root." msgstr "" #: ../fedora-image.rst:134 msgid "" "You can also use the GUI to detach and reboot it by manually stopping and " "starting." msgstr "" #: ../fedora-image.rst:137 msgid "" "Log in as root user when you boot for the first time after installation." msgstr "" #: ../fedora-image.rst:139 msgid "" "Install and run the ``acpid`` service on the guest system to enable the " "virtual machine to reboot or shutdown an instance." msgstr "" #: ../fedora-image.rst:142 msgid "" "Run the following commands inside the Fedora guest to install the ACPI " "service and configure it to start when the system boots:" msgstr "" #: ../fedora-image.rst:150 msgid "" "Install the ``cloud-init`` package inside the Fedora guest by adding the " "EPEL repo:" msgstr "" #: ../fedora-image.rst:153 msgid "" "The ``cloud-init`` package automatically fetches the public key from the " "metadata server and places the key in an account." msgstr "" #: ../fedora-image.rst:161 msgid "" "You can change the name of the account used by ``cloud-init`` by editing the " "``/etc/cloud/cloud.cfg`` file and adding a line with a different user. For " "example, to configure ``cloud-init`` to put the key in an account named " "admin, add this line to the configuration file:" msgstr "" #: ../fedora-image.rst:170 msgid "" "Disable the default ``zeroconf`` route for the instance to access the " "metadata service:" msgstr "" #: ../fedora-image.rst:177 msgid "" "For the :command:`nova console-log` command to work properly on Fedora 20, " "you might need to add the following lines to the ``/boot/grub/menu.lst`` " "file:" msgstr "" #: ../fedora-image.rst:188 msgid "Shut down the instance from inside the instance as a root user:" msgstr "" #: ../fedora-image.rst:194 msgid "Clean up and remove MAC address details." msgstr "" #: ../fedora-image.rst:203 msgid "" "Use the :command:`virt-sysprep` utility. This performs various cleanup tasks " "such as removing the MAC address references. It will clean up a virtual " "machine image in place:" msgstr "" #: ../fedora-image.rst:211 msgid "" "Undefine the domain since you no longer need to have this virtual machine " "image managed by libvirt:" msgstr "" #: ../fedora-image.rst:218 msgid "" "The underlying image file that you created with the :command:`qemu-img " "create` command is ready to be uploaded to the Image service." msgstr "" #: ../freebsd-image.rst:3 msgid "Example: FreeBSD image" msgstr "" #: ../freebsd-image.rst:5 msgid "" "This example creates a minimal FreeBSD image that is compatible with " "OpenStack and ``bsd-cloudinit``. The ``bsd-cloudinit`` program is " "independently maintained and in active development. The best source of " "information on the current state of the project is at http://pellaeon.github." "io/bsd-cloudinit/." msgstr "" #: ../freebsd-image.rst:12 msgid "" "KVM with virtio drivers is used as the virtualization platform because that " "is the most widely used among OpenStack operators. If you use a different " "platform for your cloud virtualization, use that same platform in the image " "creation step." msgstr "" #: ../freebsd-image.rst:17 msgid "" "This example shows how to create a FreeBSD 10 image. To create a FreeBSD 9.2 " "image, follow these steps with the noted differences." msgstr "" #: ../freebsd-image.rst:20 msgid "**To create a FreeBSD image**" msgstr "" #: ../freebsd-image.rst:22 msgid "Make a virtual drive:" msgstr "" #: ../freebsd-image.rst:28 msgid "" "The minimum supported disk size for FreeBSD is 1 GB. Because the goal is to " "make the smallest possible base image, the example uses that minimum size. " "This size is sufficient to include the optional ``doc``, ``games``, and " "``lib32`` collections. To include the ``ports`` collection, add another 1 " "GB. To include ``src``, add 512 MB." msgstr "" #: ../freebsd-image.rst:35 msgid "Get the installer ISO:" msgstr "" #: ../freebsd-image.rst:42 msgid "" "Launch a VM on your local workstation. Use the same hypervisor, virtual " "disk, and virtual network drivers as you use in your production environment." msgstr "" #: ../freebsd-image.rst:46 msgid "The following command uses the minimum amount of RAM, which is 256 MB:" msgstr "" #: ../freebsd-image.rst:54 msgid "" "You can specify up to 1 GB additional RAM to make the installation process " "run faster." msgstr "" #: ../freebsd-image.rst:57 msgid "This VM must also have Internet access to download packages." msgstr "" #: ../freebsd-image.rst:61 msgid "" "By using the same hypervisor, you can ensure that you emulate the same " "devices that exist in production. However, if you use full hardware " "virtualization instead of paravirtualization, you do not need to use the " "same hypervisor; you must use the same type of virtualized hardware because " "FreeBSD device names are related to their drivers. If the name of your root " "block device or primary network interface in production differs than the " "names used during image creation, errors can occur." msgstr "" #: ../freebsd-image.rst:71 msgid "" "You now have a VM that boots from the downloaded install ISO and is " "connected to the blank virtual disk that you created previously." msgstr "" #: ../freebsd-image.rst:74 msgid "" "To install the operating system, complete the following steps inside the VM:" msgstr "" #: ../freebsd-image.rst:77 msgid "When prompted, choose to run the ISO in :guilabel:`Install` mode." msgstr "" #: ../freebsd-image.rst:79 msgid "" "Accept the default keymap or select an appropriate mapping for your needs." msgstr "" #: ../freebsd-image.rst:82 msgid "" "Provide a host name for your image. If you use ``bsd-cloudinit``, it " "overrides this value with the name provided by OpenStack when an instance " "boots from this image." msgstr "" #: ../freebsd-image.rst:86 msgid "" "When prompted about the optional ``doc``, ``games``, ``lib32``, ``ports``, " "and ``src`` system components, select only those that you need. It is " "possible to have a fully functional installation without selecting " "additional components selected. As noted previously, a minimal system with a " "1 GB virtual disk supports ``doc``, ``games``, and ``lib32`` inclusive. The " "``ports`` collection requires at least 1 GB additional space and possibly " "more if you plan to install many ports. The ``src`` collection requires an " "additional 512 MB." msgstr "" #: ../freebsd-image.rst:97 msgid "" "Configure the primary network interface to use DHCP. In this example, which " "uses a virtio network device, this interface is named ``vtnet0``." msgstr "" #: ../freebsd-image.rst:101 msgid "Accept the default network mirror." msgstr "" #: ../freebsd-image.rst:103 msgid "Set up disk partitioning." msgstr "" #: ../freebsd-image.rst:105 msgid "" "Disk partitioning is a critical element of the image creation process and " "the auto-generated default partitioning scheme does not work with ``bsd-" "cloudinit`` at this time." msgstr "" #: ../freebsd-image.rst:109 msgid "" "Because the default does not work, you must select manual partitioning. The " "partition editor should list only one block device. If you use virtio for " "the disk device driver, it is named ``vtbd0``. Select this device and run " "the :command:`create` command three times:" msgstr "" #: ../freebsd-image.rst:115 msgid "" "Select :guilabel:`Create` to create a partition table. This action is the " "default when no partition table exists. Then, select :guilabel:`GPT GUID " "Partition Table` from the list. This choice is the default." msgstr "" #: ../freebsd-image.rst:120 msgid "Create two partitions:" msgstr "" #: ../freebsd-image.rst:122 msgid "" "First partition: A 64 kB ``freebsd-boot`` partition with no mount point." msgstr "" #: ../freebsd-image.rst:124 msgid "" "Second partition: A ``freebsd-ufs`` partition with a mount point of ``/`` " "with all remaining free space." msgstr "" #: ../freebsd-image.rst:127 msgid "" "The following figure shows a completed partition table with a 1 GB virtual " "disk:" msgstr "" #: ../freebsd-image.rst:133 msgid "" "Select :guilabel:`Finish` and then :guilabel:`Commit` to commit your changes." msgstr "" #: ../freebsd-image.rst:138 msgid "" "If you modify this example, the root partition, which is mounted on ``/``, " "must be the last partition on the drive so that it can expand at run time to " "the disk size that your instance type provides. Also note that ``bsd-" "cloudinit`` currently has a hard-coded assumption that this is the second " "partition." msgstr "" #: ../freebsd-image.rst:145 msgid "Select a root password." msgstr "" #: ../freebsd-image.rst:147 msgid "Select the CMOS time zone." msgstr "" #: ../freebsd-image.rst:149 msgid "" "The virtualized CMOS almost always stores its time in UTC, so unless you " "know otherwise, select UTC." msgstr "" #: ../freebsd-image.rst:152 msgid "Select the time zone appropriate to your environment." msgstr "" #: ../freebsd-image.rst:154 msgid "" "From the list of services to start on boot, you must select :guilabel:`ssh`. " "Optionally, select other services." msgstr "" #: ../freebsd-image.rst:157 msgid "Optionally, add users." msgstr "" #: ../freebsd-image.rst:159 msgid "" "You do not need to add users at this time. The ``bsd-cloudinit`` program " "adds a ``freebsd`` user account if one does not exist. The ``ssh`` keys for " "this user are associated with OpenStack. To customize this user account, you " "can create it now. For example, you might want to customize the shell for " "the user." msgstr "" #: ../freebsd-image.rst:166 msgid "Final config" msgstr "" #: ../freebsd-image.rst:168 msgid "" "This menu enables you to update previous settings. Check that the settings " "are correct, and click :guilabel:`exit`." msgstr "" #: ../freebsd-image.rst:171 msgid "" "After you exit, you can open a shell to complete manual configuration steps. " "Select :guilabel:`Yes` to make a few OpenStack-specific changes:" msgstr "" #: ../freebsd-image.rst:175 msgid "Set up the console:" msgstr "" #: ../freebsd-image.rst:181 msgid "" "This sets console output to go to the serial console, which is displayed by :" "command:`nova consolelog`, and the video console for sites with VNC or Spice " "configured." msgstr "" #: ../freebsd-image.rst:185 msgid "Minimize boot delay:" msgstr "" #: ../freebsd-image.rst:191 msgid "" "Download the latest ``bsd-cloudinit-installer``. The download commands " "differ between FreeBSD 10.1 and 9.2 because of differences in how the :" "command:`fetch` command handles HTTPS URLs." msgstr "" #: ../freebsd-image.rst:196 msgid "" "In FreeBSD 10.1 the :command:`fetch` command verifies SSL peers by default, " "so you need to install the ``ca_root_nss`` package that contains certificate " "authority root certificates and tell :command:`fetch` where to find them. " "For FreeBSD 10.1 run these commands:" msgstr "" #: ../freebsd-image.rst:208 msgid "" "FreeBSD 9.2 :command:`fetch` does not support peer-verification for https. " "For FreeBSD 9.2, run this command:" msgstr "" #: ../freebsd-image.rst:215 msgid "Run the installer:" msgstr "" #: ../freebsd-image.rst:221 msgid "" "Issue this command to download and install the latest ``bsd-cloudinit`` " "package, and install the necessary prerequisites." msgstr "" #: ../freebsd-image.rst:224 msgid "" "Install ``sudo`` and configure the ``freebsd`` user to have passwordless " "access:" msgstr "" #: ../freebsd-image.rst:232 msgid "Power off the system:" msgstr "" #: ../image-formats.rst:3 msgid "Disk and container formats for images" msgstr "" #: ../image-formats.rst:5 msgid "" "When you add an image to the Image service, you can specify its disk and " "container formats." msgstr "" #: ../image-formats.rst:9 msgid "Disk formats" msgstr "" #: ../image-formats.rst:11 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 "" #: ../image-formats.rst:16 msgid "Set the disk format for your image to one of the following values:" msgstr "" #: ../image-formats.rst:18 ../image-formats.rst:56 msgid "aki" msgstr "" #: ../image-formats.rst:19 ../image-formats.rst:57 msgid "An Amazon kernel image." msgstr "" #: ../image-formats.rst:20 ../image-formats.rst:58 msgid "ami" msgstr "" #: ../image-formats.rst:21 ../image-formats.rst:59 msgid "An Amazon machine image." msgstr "" #: ../image-formats.rst:22 ../image-formats.rst:60 msgid "ari" msgstr "" #: ../image-formats.rst:23 ../image-formats.rst:61 msgid "An Amazon ramdisk image." msgstr "" #: ../image-formats.rst:25 msgid "" "An archive format for the data contents of an optical disc, such as CD-ROM." msgstr "" #: ../image-formats.rst:25 msgid "iso" msgstr "" #: ../image-formats.rst:28 msgid "" "Supported by the QEMU emulator that can expand dynamically and supports Copy " "on Write." msgstr "" #: ../image-formats.rst:28 msgid "qcow2" msgstr "" #: ../image-formats.rst:31 msgid "" "An unstructured disk image format; if you have a file without an extension " "it is possibly a raw format." msgstr "" #: ../image-formats.rst:33 msgid "vdi" msgstr "" #: ../image-formats.rst:34 msgid "Supported by VirtualBox virtual machine monitor and the QEMU emulator." msgstr "" #: ../image-formats.rst:36 msgid "" "The VHD disk format, a common disk format used by virtual machine monitors " "from VMware, Xen, Microsoft, VirtualBox, and others." msgstr "" #: ../image-formats.rst:36 msgid "vhd" msgstr "" #: ../image-formats.rst:39 msgid "Common disk format supported by many common virtual machine monitors." msgstr "" #: ../image-formats.rst:39 msgid "vmdk" msgstr "" #: ../image-formats.rst:42 msgid "Container formats" msgstr "" #: ../image-formats.rst:44 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 "" #: ../image-formats.rst:49 msgid "" "The Image service and other OpenStack projects do not currently support the " "container format. It is safe to specify ``bare`` as the container format if " "you are unsure." msgstr "" #: ../image-formats.rst:53 msgid "" "You can set the container format for your image to one of the following " "values:" msgstr "" #: ../image-formats.rst:62 msgid "bare" msgstr "" #: ../image-formats.rst:63 msgid "The image does not have a container or metadata envelope." msgstr "" #: ../image-formats.rst:64 msgid "docker" msgstr "" #: ../image-formats.rst:65 msgid "A docker container format." msgstr "" #: ../image-formats.rst:66 msgid "ovf" msgstr "" #: ../image-formats.rst:67 msgid "The OVF container format." msgstr "" #: ../image-metadata.rst:3 msgid "Image metadata" msgstr "" #: ../image-metadata.rst:5 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 "" #: ../image-metadata.rst:9 msgid "" "Metadata can also determine the scheduling of hosts. If the ``property`` " "option is set on an image, and Compute is configured so that the " "``ImagePropertiesFilter`` scheduler filter is enabled (default), then the " "scheduler only considers compute hosts that satisfy that property." msgstr "" #: ../image-metadata.rst:17 msgid "" "Compute's ``ImagePropertiesFilter`` value is specified in the " "``scheduler_default_filter`` value in the ``/etc/nova/nova.conf`` file." msgstr "" #: ../image-metadata.rst:20 msgid "" "You can add metadata to Image service images by using the ``--property " "key=value`` parameter with the :command:`openstack image create` or :command:" "`openstack image set` command. More than one property can be specified. For " "example:" msgstr "" #: ../image-metadata.rst:30 msgid "" "Common image properties are also specified in the ``/etc/glance/schema-image." "json`` file. For a complete list of valid property keys and values, refer to " "the `OpenStack Command-Line Reference `_." msgstr "" #: ../image-metadata.rst:36 msgid "" "All associated properties for an image can be displayed using the :command:" "`openstack image show` command. For example:" msgstr "" #: ../image-metadata.rst:67 msgid "**Volume-from-Image properties**" msgstr "" #: ../image-metadata.rst:69 msgid "" "When creating Block Storage volumes from images, also consider your " "configured image properties. If you alter the core image properties, you " "should also update your Block Storage configuration. Amend " "``glance_core_properties`` in the ``/etc/cinder/cinder.conf`` file on all " "controller nodes to match the core properties you have set in the Image " "service." msgstr "" #: ../image-metadata.rst:77 msgid "Metadata definition service" msgstr "" #: ../image-metadata.rst:79 msgid "With this service you can define:" msgstr "" #: ../image-metadata.rst:82 msgid "Contains metadata definitons." msgstr "" #: ../image-metadata.rst:84 msgid "" "Specifies the access controls for everything defined in the namespace. These " "access controls determine who can define and use the definitions in the " "namespace." msgstr "" #: ../image-metadata.rst:88 msgid "Associates the definitions with different types of resources." msgstr "" #: ../image-metadata.rst:88 msgid "Namespace" msgstr "" #: ../image-metadata.rst:91 msgid "" "A single property and its primitive constraints. Each property can only be a " "primitive type. For example, string, integer, number, boolean, or array." msgstr "" #: ../image-metadata.rst:92 msgid "Property" msgstr "" #: ../image-metadata.rst:95 msgid "" "Describes a group of one to many properties and their primitive constraints. " "Each property in the group can only be a primitive type. For example, " "string, integer, number, boolean, or array." msgstr "" #: ../image-metadata.rst:99 msgid "" "The object may optionally define required properties under the semantic " "understanding that if you use the object, you should provide all required " "properties." msgstr "" #: ../image-metadata.rst:101 msgid "Object" msgstr "" #: ../image-metadata.rst:104 msgid "" "Specifies the relationship between resource types and the namespaces that " "are applicable to them. This information can be used to drive UI and CLI " "views. For example, the same namespace of objects, properties, and tags may " "be used for images, snapshots, volumes, and flavors. Or a namespace may only " "apply to images." msgstr "" #: ../image-metadata.rst:108 msgid "Resource type association" msgstr "" #: ../image-metadata.rst:110 msgid "" "The Image service has predefined namespaces for the metadata definitions " "catalog. To load files from this directory into the database:" msgstr "" #: ../image-metadata.rst:117 msgid "To unload the files from the database:" msgstr "" #: ../image-metadata.rst:123 msgid "To export the definitions in JSON format:" msgstr "" #: ../image-metadata.rst:131 msgid "" "By default, files are loaded from and exported to the Image service's ``/etc/" "glance/metadefs`` directory." msgstr "" #: ../index.rst:3 msgid "OpenStack Virtual Machine Image Guide" msgstr "" #: ../index.rst:6 msgid "Abstract" msgstr "" #: ../index.rst:8 msgid "" "This guide describes how to obtain, create, and modify virtual machine " "images that are compatible with OpenStack." msgstr "" #: ../index.rst:12 msgid "Contents" msgstr "" #: ../index.rst:31 msgid "Search in this guide" msgstr "" #: ../index.rst:33 msgid ":ref:`search`" msgstr "" #: ../introduction.rst:3 msgid "Introduction" msgstr "" #: ../introduction.rst:11 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 "" #: ../introduction.rst:16 msgid "" "To keep things brief, we will sometimes use the term ``image`` instead of " "virtual machine image." msgstr "" #: ../introduction.rst:19 msgid "**What is a virtual machine image?**" msgstr "" #: ../introduction.rst:21 msgid "" "A virtual machine image is a single file which contains a virtual disk that " "has a bootable operating system installed on it." msgstr "" #: ../introduction.rst:24 msgid "" "Virtual machine images come in different formats, some of which are " "described below." msgstr "" #: ../introduction.rst:28 msgid "" "The `AKI/AMI/ARI `_ format was the initial image format supported by Amazon EC2. The " "image consists of three files:" msgstr "" #: ../introduction.rst:34 msgid "" "A kernel file that the hypervisor will load initially to boot the image. For " "a Linux machine, this would be a ``vmlinuz`` file." msgstr "" #: ../introduction.rst:35 msgid "AKI (Amazon Kernel Image)" msgstr "" #: ../introduction.rst:38 msgid "AMI (Amazon Machine Image)" msgstr "" #: ../introduction.rst:38 msgid "This is a virtual machine image in raw format, as described above." msgstr "" #: ../introduction.rst:41 msgid "" "An optional ramdisk file mounted at boot time. For a Linux machine, this " "would be an ``initrd`` file." msgstr "" #: ../introduction.rst:42 msgid "AKI/AMI/ARI" msgstr "" #: ../introduction.rst:42 msgid "ARI (Amazon Ramdisk Image)" msgstr "" #: ../introduction.rst:45 msgid "" "The `ISO `_ 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 do " "not 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 "" #: ../introduction.rst:51 msgid "ISO" msgstr "" #: ../introduction.rst:54 msgid "" "`OVF `_ " "(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 "" #: ../introduction.rst:61 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 "" #: ../introduction.rst:65 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 "" #: ../introduction.rst:67 msgid "OVF" msgstr "" #: ../introduction.rst:70 msgid "" "The `QCOW2 `_ (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:" msgstr "" #: ../introduction.rst:75 msgid "Using sparse representation, so the image size is smaller." msgstr "" #: ../introduction.rst:76 msgid "Support for snapshots." msgstr "" #: ../introduction.rst:78 msgid "" "Because qcow2 is sparse, qcow2 images are typically smaller than raw images. " "Smaller images mean faster uploads, so it is often faster to convert a raw " "image to qcow2 for uploading instead of uploading the raw file directly." msgstr "" #: ../introduction.rst:85 msgid "" "Because raw images do not support snapshots, OpenStack Compute will " "automatically convert raw image files to qcow2 as needed." msgstr "" #: ../introduction.rst:86 msgid "QCOW2" msgstr "" #: ../introduction.rst:89 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, " "``/dev/sda`` to a file using the :command:`dd` command." msgstr "" #: ../introduction.rst:97 msgid "" "We do not recommend creating raw images by dd'ing block device files, we " "discuss how to create raw images later." msgstr "" #: ../introduction.rst:98 msgid "Raw" msgstr "" #: ../introduction.rst:101 msgid "" "A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains " "an AMI file, AKI file, and ARI file." msgstr "" #: ../introduction.rst:106 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 "" #: ../introduction.rst:108 msgid "UEC tarball" msgstr "" #: ../introduction.rst:111 msgid "" "VirtualBox uses the `VDI `_ (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 "" #: ../introduction.rst:115 msgid "VDI" msgstr "" #: ../introduction.rst:118 msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." msgstr "" #: ../introduction.rst:118 msgid "VHD" msgstr "" #: ../introduction.rst:121 msgid "" "The version of Hyper-V that ships with Microsoft Server 2012 uses the newer " "`VHDX `_ format, " "which has some additional features over VHD such as support for larger disk " "sizes and protection against data corruption during power failures." msgstr "" #: ../introduction.rst:124 msgid "VHDX" msgstr "" #: ../introduction.rst:127 msgid "" "VMware ESXi hypervisor uses the `VMDK `_ (Virtual Machine Disk) format for images." msgstr "" #: ../introduction.rst:128 msgid "VMDK" msgstr "" #: ../modify-images.rst:3 msgid "Modify images" msgstr "" #: ../modify-images.rst:5 msgid "" "Once you have obtained a virtual machine image, you may want to make some " "changes to it before uploading it to the Image service. Here we describe " "several tools available that allow you to modify images." msgstr "" #: ../modify-images.rst:11 msgid "" "Do not attempt to use these tools to modify an image that is attached to a " "running virtual machine. These tools are designed only to modify the images " "that are not currently running." msgstr "" #: ../modify-images.rst:17 msgid "guestfish" msgstr "" #: ../modify-images.rst:19 msgid "" "The ``guestfish`` program is a tool from the `libguestfs `_ project that allows you to modify the files inside of a virtual " "machine image." msgstr "" #: ../modify-images.rst:25 msgid "" "``guestfish`` 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 :command:`guestfish` commands, such as :" "command:`touch`, :command:`chmod`, and :command:`rm`, resemble traditional " "bash commands." msgstr "" #: ../modify-images.rst:32 msgid "Example guestfish session" msgstr "" #: ../modify-images.rst:34 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. This is because the MAC address is different " "when the virtual machine images boots. This example shows how to use the " "``guestfish`` to remove references to the old MAC address by deleting the ``/" "etc/udev/rules.d/70-persistent-net.rules`` file and removing the ``HWADDR`` " "line from the ``/etc/sysconfig/network-scripts/ifcfg-eth0`` file." msgstr "" #: ../modify-images.rst:45 msgid "" "Assume that you have a CentOS qcow2 image called ``centos63_desktop.img``. " "Mount the image in read-write mode as root, as follows:" msgstr "" #: ../modify-images.rst:61 msgid "This starts a guestfish session." msgstr "" #: ../modify-images.rst:65 msgid "the guestfish prompt looks like a fish: ``>``." msgstr "" #: ../modify-images.rst:67 msgid "" "We must first use the :command:`run` 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." msgstr "" #: ../modify-images.rst:76 msgid "" "We can now view the file systems in the image using the :command:`list-" "filesystems` command:" msgstr "" #: ../modify-images.rst:86 msgid "We need to mount the logical volume that contains the root partition:" msgstr "" #: ../modify-images.rst:92 msgid "" "Next, we want to delete a file. We can use the :command:`rm` guestfish " "command, which works the same way it does in a traditional shell." msgstr "" #: ../modify-images.rst:99 msgid "" "We want to edit the ``ifcfg-eth0`` file to remove the ``HWADDR`` line. The :" "command:`edit` command will copy the file to the host, invoke your editor, " "and then copy the file back." msgstr "" #: ../modify-images.rst:107 msgid "" "If you want to modify this image to load the 8021q kernel at boot time, you " "must create an executable script in the ``/etc/sysconfig/modules/`` " "directory. You can use the :command:`touch` guestfish command to create an " "empty file, the :command:`edit` command to edit it, and the :command:`chmod` " "command to make it executable." msgstr "" #: ../modify-images.rst:119 msgid "We add the following line to the file and save it:" msgstr "" #: ../modify-images.rst:125 msgid "Then we set to executable:" msgstr "" #: ../modify-images.rst:131 msgid "We are done, so we can exit using the :command:`exit` command:" msgstr "" #: ../modify-images.rst:138 msgid "Go further with guestfish" msgstr "" #: ../modify-images.rst:140 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 `guestfs-recipes `_ documentation page for a sense of what is possible with these tools." msgstr "" #: ../modify-images.rst:147 msgid "guestmount" msgstr "" #: ../modify-images.rst:149 msgid "" "For some types of changes, you may find it easier to mount the image's file " "system directly in the guest. The ``guestmount`` program, also from the " "libguestfs project, allows you to do so." msgstr "" #: ../modify-images.rst:154 msgid "" "For example, to mount the root partition from our ``centos63_desktop.qcow2`` " "image to ``/mnt``, we can do:" msgstr "" #: ../modify-images.rst:161 msgid "" "If we did not know in advance what the mount point is in the guest, we could " "use the ``-i`` (inspect) flag to tell guestmount to automatically determine " "what mount point to use:" msgstr "" #: ../modify-images.rst:169 msgid "" "Once mounted, we could do things like list the installed packages using rpm:" msgstr "" #: ../modify-images.rst:175 msgid "Once done, we unmount:" msgstr "" #: ../modify-images.rst:182 msgid "virt-* tools" msgstr "" #: ../modify-images.rst:184 msgid "" "The `libguestfs `_ project has a number of other " "useful tools, including:" msgstr "" #: ../modify-images.rst:187 msgid "" "`virt-edit `_ for editing a file " "inside of an image." msgstr "" #: ../modify-images.rst:189 msgid "" "`virt-df `_ for displaying free space " "inside of an image." msgstr "" #: ../modify-images.rst:191 msgid "" "`virt-resize `_ for resizing an " "image." msgstr "" #: ../modify-images.rst:193 msgid "" "`virt-sysprep `_ for preparing an " "image for distribution (for example, delete SSH host keys, remove MAC " "address info, or remove user accounts)." msgstr "" #: ../modify-images.rst:196 msgid "" "`virt-sparsify `_ for making an " "image sparse." msgstr "" #: ../modify-images.rst:198 msgid "" "`virt-p2v `_ for converting a physical " "machine to an image that runs on KVM." msgstr "" #: ../modify-images.rst:200 msgid "" "`virt-v2v `_ for converting Xen and VMware " "images to KVM images." msgstr "" #: ../modify-images.rst:204 msgid "Modify a single file inside of an image" msgstr "" #: ../modify-images.rst:206 msgid "" "This example shows how to use :command:`virt-edit` to modify a file. The " "command can take either a filename as an argument with the ``-a`` flag, or a " "domain name as an argument with the ``-d`` flag. The following examples " "shows how to use this to modify the ``/etc/shadow`` file in instance with " "libvirt domain name ``instance-000000e1`` that is currently running:" msgstr "" #: ../modify-images.rst:220 msgid "Resize an image" msgstr "" #: ../modify-images.rst:222 msgid "" "Here is an example of how to use :command:`virt-resize` to resize an image. " "Assume we have a 16 GB Windows image in qcow2 format that we want to resize " "to 50 GB." msgstr "" #: ../modify-images.rst:226 msgid "First, we use :command:`virt-filesystems` to identify the partitions:" msgstr "" #: ../modify-images.rst:236 msgid "" "In this case, it is the ``/dev/sda2`` partition that we want to resize. We " "create a new qcow2 image and use the :command:`virt-resize` command to write " "a resized copy of the original into the new image:" msgstr "" #: ../modify-images.rst:268 msgid "Loop devices, kpartx, network block devices" msgstr "" #: ../modify-images.rst:270 msgid "" "If you do not have access to the libguestfs, you can mount image file " "systems directly in the host using loop devices, kpartx, and network block " "devices." msgstr "" #: ../modify-images.rst:276 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 `A reminder why you should never " "mount guest disk images on the host OS `_ by Daniel Berrangé for more details." msgstr "" #: ../modify-images.rst:285 msgid "Mount a raw image (without LVM)" msgstr "" #: ../modify-images.rst:287 msgid "" "If you have a raw virtual machine image that is not using LVM to manage its " "partitions, use the :command:`losetup` command to find an unused loop device." msgstr "" #: ../modify-images.rst:296 msgid "" "In this example, ``/dev/loop0`` is free. Associate a loop device with the " "raw image:" msgstr "" #: ../modify-images.rst:303 msgid "" "If the image only has a single partition, you can mount the loop device " "directly:" msgstr "" #: ../modify-images.rst:310 msgid "" "If the image has multiple partitions, use :command:`kpartx` to expose the " "partitions as separate devices (for example, ``/dev/mapper/loop0p1``), then " "mount the partition that corresponds to the root file system:" msgstr "" #: ../modify-images.rst:318 msgid "" "If the image has, say three partitions (/boot, /, swap), there should be one " "new device created per partition:" msgstr "" #: ../modify-images.rst:328 msgid "To mount the second partition, as root:" msgstr "" #: ../modify-images.rst:335 msgid "Once you are done, to clean up:" msgstr "" #: ../modify-images.rst:345 msgid "Mount a raw image (with LVM)" msgstr "" #: ../modify-images.rst:347 msgid "" "If your partitions are managed with LVM, use :command:`losetup` and :command:" "`kpartx` commands as in the previous example to expose the partitions to the " "host." msgstr "" #: ../modify-images.rst:358 msgid "" "Next, you need to use the :command:`vgscan` command to identify the LVM " "volume groups and then the :command:`vgchange` command to expose the volumes " "as devices:" msgstr "" #: ../modify-images.rst:371 msgid "Clean up when you are done:" msgstr "" #: ../modify-images.rst:381 msgid "Mount a qcow2 image (without LVM)" msgstr "" #: ../modify-images.rst:383 msgid "" "You need the ``nbd`` (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:" msgstr "" #: ../modify-images.rst:391 msgid "" "Assuming the first block device (``/dev/nbd0``) is not currently in use, we " "can expose the disk partitions using the :command:`qemu-nbd` and :command:" "`partprobe` commands. As root:" msgstr "" #: ../modify-images.rst:400 msgid "" "If the image has, say three partitions (/boot, /, swap), there should be one " "new device created for each partition:" msgstr "" #: ../modify-images.rst:413 msgid "" "If the network block device you selected was already in use, the initial :" "command:`qemu-nbd` command will fail silently, and the ``/dev/nbd3p{1,2,3}`` " "device files will not be created." msgstr "" #: ../modify-images.rst:417 msgid "" "If the image partitions are not managed with LVM, they can be mounted " "directly:" msgstr "" #: ../modify-images.rst:425 ../modify-images.rst:453 msgid "When you are done, clean up:" msgstr "" #: ../modify-images.rst:434 msgid "Mount a qcow2 image (with LVM)" msgstr "" #: ../modify-images.rst:436 msgid "" "If the image partitions are managed with LVM, after you use :command:`qemu-" "nbd` and :command:`partprobe`, you must use :command:`vgscan` and :command:" "`vgchange -ay` in order to expose the LVM partitions as devices that can be " "mounted:" msgstr "" #: ../net-running.rst:3 msgid "Verify the libvirt default network is running" msgstr "" #: ../net-running.rst:5 msgid "" "Before starting a virtual machine with libvirt, verify that the libvirt " "``default`` network has 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 ``virbr0``), iptables " "rules, and a dnsmasq process that will serve as a DHCP server." msgstr "" #: ../net-running.rst:13 msgid "" "To verify that the libvirt ``default`` network is enabled, use the :command:" "`virsh net-list` command and verify that the ``default`` network is active:" msgstr "" #: ../net-running.rst:24 msgid "If the network is not active, start it by doing:" msgstr "" #: ../obtain-images.rst:3 msgid "Get images" msgstr "" #: ../obtain-images.rst:5 msgid "" "The simplest way to obtain a virtual machine image that works with OpenStack " "is to download one that someone else has already created. Most of the images " "contain the ``cloud-init`` package to support the SSH key pair and user data " "injection. Because many of the images disable SSH password authentication by " "default, boot the image with an injected key pair. You can ``SSH`` into the " "instance with the private key and default login account. See the `OpenStack " "End User Guide `_ for more information on " "how to create and inject key pairs with OpenStack." msgstr "" #: ../obtain-images.rst:17 msgid "CentOS images" msgstr "" #: ../obtain-images.rst:19 msgid "The CentOS project maintains official images for direct download." msgstr "" #: ../obtain-images.rst:21 msgid "`CentOS 6 images `_" msgstr "" #: ../obtain-images.rst:22 msgid "`CentOS 7 images `_" msgstr "" #: ../obtain-images.rst:26 msgid "In a CentOS cloud image, the login account is ``centos``." msgstr "" #: ../obtain-images.rst:29 msgid "CirrOS (test) images" msgstr "" #: ../obtain-images.rst:31 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 `CirrOS download page `_." msgstr "" #: ../obtain-images.rst:36 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 " "`cirros-0.3.4-x86_64-disk.img `_." msgstr "" #: ../obtain-images.rst:43 msgid "" "In a CirrOS image, the login account is ``cirros``. The password is " "``cubswin:)``." msgstr "" #: ../obtain-images.rst:47 msgid "Official Ubuntu images" msgstr "" #: ../obtain-images.rst:49 msgid "" "Canonical maintains an official set of `Ubuntu-based images `_." msgstr "" #: ../obtain-images.rst:52 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 14.04 Trusty Tahr is http://cloud-" "images.ubuntu.com/trusty/current/. Scroll to the bottom of the page for " "links to the images that can be downloaded directly." msgstr "" #: ../obtain-images.rst:59 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 14.04 " "is `trusty-server-cloudimg-amd64-disk1.img `_." msgstr "" #: ../obtain-images.rst:67 msgid "In an Ubuntu cloud image, the login account is ``ubuntu``." msgstr "" #: ../obtain-images.rst:70 msgid "Official Red Hat Enterprise Linux images" msgstr "" #: ../obtain-images.rst:72 msgid "" "Red Hat maintains official Red Hat Enterprise Linux cloud images. A valid " "Red Hat Enterprise Linux subscription is required to download these images." msgstr "" #: ../obtain-images.rst:76 msgid "" "`Red Hat Enterprise Linux 7 KVM Guest Image `_" msgstr "" #: ../obtain-images.rst:78 msgid "" "`Red Hat Enterprise Linux 6 KVM Guest Image `_" msgstr "" #: ../obtain-images.rst:83 msgid "In a RHEL cloud image, the login account is ``cloud-user``." msgstr "" #: ../obtain-images.rst:86 msgid "Official Fedora images" msgstr "" #: ../obtain-images.rst:88 msgid "" "The Fedora project maintains a list of official cloud images at https://" "getfedora.org/cloud/download/." msgstr "" #: ../obtain-images.rst:93 msgid "In a Fedora cloud image, the login account is ``fedora``." msgstr "" #: ../obtain-images.rst:96 msgid "Official openSUSE and SLES images" msgstr "" #: ../obtain-images.rst:98 msgid "" "SUSE provides images for `openSUSE `_. For SUSE Linux Enterprise Server (SLES), " "custom images can be built with a web-based tool called `SUSE Studio " "`_. SUSE Studio can also be used to build the custom " "openSUSE images." msgstr "" #: ../obtain-images.rst:105 msgid "Official Debian images" msgstr "" #: ../obtain-images.rst:107 msgid "" "Since January 2015, `Debian provides images for direct download `_. They are now made at the same time " "as the CD and DVD images of Debian. Therefore, images are available on each " "point release of Debian. Also, weekly images of the testing distribution are " "available." msgstr "" #: ../obtain-images.rst:115 msgid "In a Debian image, the login account is ``debian``." msgstr "" #: ../obtain-images.rst:118 msgid "Official images from other Linux distributions" msgstr "" #: ../obtain-images.rst:120 msgid "" "As of this writing, we are not aware of other distributions that provide " "images for download." msgstr "" #: ../obtain-images.rst:124 msgid "Microsoft Windows images" msgstr "" #: ../obtain-images.rst:126 msgid "" "Cloudbase Solutions hosts `Windows Cloud Images `_ that runs on Hyper-V, KVM, and XenServer/XCP." msgstr "" #: ../openstack-images.rst:0 msgid "Image cache management configuration options" msgstr "" #: ../openstack-images.rst:3 msgid "OpenStack Linux image requirements" msgstr "" #: ../openstack-images.rst:5 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 " "requirements by installing the `cloud-init `_ 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 "" #: ../openstack-images.rst:12 msgid "Disk partitions and resize root partition on boot (``cloud-init``)" msgstr "" #: ../openstack-images.rst:13 ../openstack-images.rst:138 msgid "No hard-coded MAC address information" msgstr "" #: ../openstack-images.rst:14 msgid "SSH server running" msgstr "" #: ../openstack-images.rst:15 ../openstack-images.rst:170 msgid "Disable firewall" msgstr "" #: ../openstack-images.rst:16 msgid "Access instance using ssh public key (``cloud-init``)" msgstr "" #: ../openstack-images.rst:17 msgid "Process user data and other metadata (``cloud-init``)" msgstr "" #: ../openstack-images.rst:18 msgid "" "Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux " "kernel version < 3.0)" msgstr "" #: ../openstack-images.rst:22 msgid "Disk partitions and resize root partition on boot (cloud-init)" msgstr "" #: ../openstack-images.rst:24 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 "" #: ../openstack-images.rst:28 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 ``m1.small``. 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 "" #: ../openstack-images.rst:38 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 "" #: ../openstack-images.rst:46 msgid "Xen: one ext3/ext4 partition (no LVM)" msgstr "" #: ../openstack-images.rst:48 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 "" #: ../openstack-images.rst:52 msgid "" "``auto_disk_config=True`` is set as a property on the image in the image " "registry." msgstr "" #: ../openstack-images.rst:54 msgid "The disk on the image has only one partition." msgstr "" #: ../openstack-images.rst:55 msgid "The file system on the one partition is ext3 or ext4." msgstr "" #: ../openstack-images.rst:57 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 "" #: ../openstack-images.rst:62 msgid "Non-Xen with cloud-init/cloud-tools: one ext3/ext4 partition (no LVM)" msgstr "" #: ../openstack-images.rst:64 msgid "You must configure these items for your image:" msgstr "" #: ../openstack-images.rst:66 msgid "" "The partition table for the image describes the original size of the image." msgstr "" #: ../openstack-images.rst:67 msgid "The file system for the image fills the original size of the image." msgstr "" #: ../openstack-images.rst:69 msgid "Then, during the boot process, you must:" msgstr "" #: ../openstack-images.rst:71 msgid "Modify the partition table to make it aware of the additional space:" msgstr "" #: ../openstack-images.rst:73 msgid "" "If you do not use LVM, you must modify the table to extend the existing root " "partition to encompass this additional space." msgstr "" #: ../openstack-images.rst:76 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 "" #: ../openstack-images.rst:80 msgid "Resize the root volume file system." msgstr "" #: ../openstack-images.rst:82 msgid "The simplest way to support this is to install in your image the:" msgstr "" #: ../openstack-images.rst:84 msgid "" "`cloud-utils `_ package, which contains " "the ``growpart`` tool for extending partitions." msgstr "" #: ../openstack-images.rst:86 msgid "" "`cloud-initramfs-growroot `_ " "package for Ubuntu, Debian and Fedora, which supports resizing root " "partition on the first boot." msgstr "" #: ../openstack-images.rst:89 msgid "``cloud-initramfs-growroot`` package for CentOS and RHEL." msgstr "" #: ../openstack-images.rst:90 msgid "`cloud-init `__ package." msgstr "" #: ../openstack-images.rst:92 msgid "" "With these packages installed, the image performs the root partition resize " "on boot. For example, in the ``/etc/rc.local`` 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 "" #: ../openstack-images.rst:97 msgid "" "If you cannot install ``cloud-initramfs-tools``, Robert Plestenjak has a " "GitHub project called `linux-rootfs-resize `_ that contains scripts that update a ramdisk by using " "``growpart`` so that the image resizes properly on boot." msgstr "" #: ../openstack-images.rst:103 msgid "" "If you can install the cloud-utils and ``cloud-init`` packages, we recommend " "that when you create your images, you create a single ext3 or ext4 partition " "(not managed by LVM)." msgstr "" #: ../openstack-images.rst:108 msgid "Non-Xen without cloud-init/cloud-tools: LVM" msgstr "" #: ../openstack-images.rst:110 msgid "" "If you cannot install ``cloud-init`` and ``cloud-tools`` 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 "" #: ../openstack-images.rst:118 msgid "Your script must do something like the following:" msgstr "" #: ../openstack-images.rst:120 msgid "" "Detect if any additional space is available on the disk. For example, parse " "the output of ``parted /dev/sda --script \"print free\"``." msgstr "" #: ../openstack-images.rst:123 msgid "" "Create a new LVM partition with the additional space. For example, ``parted /" "dev/sda --script \"mkpart lvm ...\"``." msgstr "" #: ../openstack-images.rst:125 msgid "Create a new physical volume. For example, ``pvcreate /dev/sda6``." msgstr "" #: ../openstack-images.rst:126 msgid "" "Extend the volume group with this physical partition. For example, " "``vgextend vg00 /dev/sda6``." msgstr "" #: ../openstack-images.rst:128 msgid "" "Extend the logical volume contained the root partition by the amount of " "space. For example, ``lvextend /dev/mapper/node-root /dev/sda6``." msgstr "" #: ../openstack-images.rst:131 msgid "" "Resize the root file system. For example, ``resize2fs /dev/mapper/node-" "root``." msgstr "" #: ../openstack-images.rst:134 msgid "" "You do not need a ``/boot`` partition unless your image is an older Linux " "distribution that requires that ``/boot`` is not managed by LVM." msgstr "" #: ../openstack-images.rst:140 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 the instance boots. You should alter the following files:" msgstr "" #: ../openstack-images.rst:148 msgid "" "Replace ``/etc/udev/rules.d/70-persistent-net.rules`` with an empty file " "(contains network persistence rules, including MAC address)." msgstr "" #: ../openstack-images.rst:150 msgid "" "Replace ``/lib/udev/rules.d/75-persistent-net-generator.rules`` with an " "empty file (this generates the file above)." msgstr "" #: ../openstack-images.rst:152 msgid "" "Remove the HWADDR line from ``/etc/sysconfig/network-scripts/ifcfg-eth0`` on " "Fedora-based images." msgstr "" #: ../openstack-images.rst:157 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 "" #: ../openstack-images.rst:162 msgid "Ensure ssh server runs" msgstr "" #: ../openstack-images.rst:164 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 ``openssh-server``." msgstr "" #: ../openstack-images.rst:172 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 "" #: ../openstack-images.rst:180 msgid "Access instance by using ssh public key (cloud-init)" msgstr "" #: ../openstack-images.rst:182 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 "" #: ../openstack-images.rst:188 msgid "" "If both the XenAPI agent and ``cloud-init`` are present in an image, ``cloud-" "init`` handles ssh-key injection. The system assumes ``cloud-init`` is " "present when the image has the ``cloud_init_installed`` property." msgstr "" #: ../openstack-images.rst:196 msgid "" "The ``cloud-init`` 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 " "``ubuntu``. On Fedora-based virtual machines, the account is called ``ec2-" "user``." msgstr "" #: ../openstack-images.rst:202 msgid "" "You can change the name of the account used by ``cloud-init`` by editing the " "``/etc/cloud/cloud.cfg`` 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 configuration file so it has the line:" msgstr "" #: ../openstack-images.rst:213 msgid "Write a custom script to fetch the public key" msgstr "" #: ../openstack-images.rst:215 msgid "" "If you are unable or unwilling to install ``cloud-init`` inside the guest, " "you can write a custom script to fetch the public key and add it to a user " "account." msgstr "" #: ../openstack-images.rst:219 msgid "" "To fetch the ssh public key and add it to the root account, edit the ``/etc/" "rc.local`` file and add the following lines before the line ``touch /var/" "lock/subsys/local``. This code fragment is taken from the `rackerjoe oz-" "image-build CentOS 6 template `_." msgstr "" #: ../openstack-images.rst:262 msgid "" "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) " "with - (hyphen). If editing a file over a VNC session, make sure it is http: " "not http; and authorized_keys not authorized-keys." msgstr "" #: ../openstack-images.rst:268 msgid "Process user data and other metadata (cloud-init)" msgstr "" #: ../openstack-images.rst:270 msgid "" "In addition to the ssh public key, an image might need additional " "information from OpenStack, such as `Provide user data to instances `_, " "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 "" #: ../openstack-images.rst:279 msgid "" "You can access this information through the metadata service or referring to " "`Store metadata on the configuration drive `_. As the OpenStack metadata service is " "compatible with version 2009-04-04 of the Amazon EC2 metadata service, " "consult the Amazon EC2 documentation on `Using Instance Metadata `_ for details on how to retrieve the user data." msgstr "" #: ../openstack-images.rst:289 msgid "" "The easiest way to support this type of functionality is to install the " "``cloud-init`` package into your image, which is configured by default to " "treat user data as an executable script, and sets the host name." msgstr "" #: ../openstack-images.rst:297 msgid "Ensure image writes boot log to console" msgstr "" #: ../openstack-images.rst:299 msgid "" "You must configure the image so that the kernel writes the boot log to the " "``ttyS0`` device. In particular, the ``console=ttyS0`` argument must be " "passed to the kernel on boot." msgstr "" #: ../openstack-images.rst:303 msgid "" "If your image uses ``grub2`` as the boot loader, there should be a line in " "the grub configuration file. For example, ``/boot/grub/grub.cfg``, which " "looks something like this:" msgstr "" #: ../openstack-images.rst:311 msgid "" "If ``console=ttyS0`` does not appear, you must modify your grub " "configuration. In general, you should not update the ``grub.cfg`` directly, " "since it is automatically generated. Instead, you should edit the ``/etc/" "default/grub`` file and modify the value of the " "``GRUB_CMDLINE_LINUX_DEFAULT`` variable:" msgstr "" #: ../openstack-images.rst:321 msgid "" "Next, update the grub configuration. On Debian-based operating systems such " "as Ubuntu, run this command:" msgstr "" #: ../openstack-images.rst:328 msgid "" "On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this " "command:" msgstr "" #: ../openstack-images.rst:336 msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" msgstr "" #: ../openstack-images.rst:338 msgid "" "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel " "did not have support for 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 "" #: ../openstack-images.rst:347 msgid "Manage the image cache" msgstr "" #: ../openstack-images.rst:349 msgid "" "Use options in the ``nova.conf`` file to control whether, and for how long, " "unused base images are stored in the ``/var/lib/nova/instances/_base/``. If " "you have configured live migration of instances, all your compute nodes " "share one common ``/var/lib/nova/instances/`` directory." msgstr "" #: ../openstack-images.rst:354 msgid "" "For information about the libvirt images in OpenStack, see `The life of an " "OpenStack libvirt image from Pádraig Brady `_." msgstr "" #: ../openstack-images.rst:362 msgid "Configuration option=Default value" msgstr "" #: ../openstack-images.rst:363 msgid "(Type) Description" msgstr "" #: ../openstack-images.rst:364 msgid "preallocate_images=none" msgstr "" #: ../openstack-images.rst:365 msgid "(StrOpt) VM image preallocation mode:" msgstr "" #: ../openstack-images.rst:367 msgid "none" msgstr "" #: ../openstack-images.rst:368 msgid "No storage provisioning occurs up front." msgstr "" #: ../openstack-images.rst:370 msgid "" "Storage is fully allocated at instance start. The ``$instance_dir/`` images " "are `fallocated `_ 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 "" #: ../openstack-images.rst:374 msgid "space" msgstr "" #: ../openstack-images.rst:376 msgid "remove_unused_base_images=True" msgstr "" #: ../openstack-images.rst:377 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 "" #: ../openstack-images.rst:381 msgid "remove_unused_original_minimum_age_seconds=86400" msgstr "" #: ../openstack-images.rst:382 msgid "" "(IntOpt) Unused unresized base images younger than this are not removed. " "Default is 86400 seconds, or 24 hours." msgstr "" #: ../openstack-images.rst:384 msgid "remove_unused_resized_minimum_age_seconds=3600" msgstr "" #: ../openstack-images.rst:385 msgid "" "(IntOpt) Unused resized base images younger than this are not removed. " "Default is 3600 seconds, or one hour." msgstr "" #: ../openstack-images.rst:388 msgid "" "To see how the settings affect the deletion of a running instance, check the " "directory where the images are stored:" msgstr "" #: ../openstack-images.rst:395 msgid "In the ``/var/log/compute/compute.log`` file, look for the identifier:" msgstr "" #: ../openstack-images.rst:403 msgid "" "Because 86400 seconds (24 hours) is the default time for " "``remove_unused_original_minimum_age_seconds``, you can either wait for that " "time interval to see the base image removed, or set the value to a shorter " "time period in the ``nova.conf`` file. Restart all nova services after " "changing a setting in the ``nova.conf`` file." msgstr "" #: ../ubuntu-image.rst:3 msgid "Example: Ubuntu image" msgstr "" #: ../ubuntu-image.rst:5 msgid "" "This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image " "for a different version of Ubuntu, follow these steps with the noted " "differences." msgstr "" #: ../ubuntu-image.rst:10 msgid "Download an Ubuntu install ISO" msgstr "" #: ../ubuntu-image.rst:12 msgid "" "Because the goal is to make the smallest possible base image, this example " "uses the network installation ISO. The Ubuntu 64-bit 14.04 network installer " "ISO is at http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/" "current/images/netboot/mini.iso." msgstr "" #: ../ubuntu-image.rst:18 msgid "Start the install process" msgstr "" #: ../ubuntu-image.rst:20 msgid "" "Start the installation process by using either :command:`virt-manager` or :" "command:`virt-install` as described in the previous section. If you use :" "command:`virt-install`, do not forget to connect your VNC client to the " "virtual machine." msgstr "" #: ../ubuntu-image.rst:25 msgid "" "Assume that the name of your virtual machine image is ``ubuntu-14.04``, " "which you need to know when you use :command:`virsh` commands to manipulate " "the state of the image." msgstr "" #: ../ubuntu-image.rst:29 msgid "" "If you are using :command:`virt-manager`, the commands should look something " "like this:" msgstr "" #: ../ubuntu-image.rst:43 ../ubuntu-image.rst:65 msgid "Step through the install" msgstr "" #: ../ubuntu-image.rst:45 msgid "" "At the initial Installer boot menu, choose the :guilabel:`Install` option. " "Step through the install prompts, the defaults should be fine." msgstr "" #: ../ubuntu-image.rst:54 msgid "" "The installer may ask you to choose a host name. The default (``ubuntu``) is " "fine. We will install the cloud-init package later, which will set the host " "name on boot when a new instance is provisioned using this image." msgstr "" #: ../ubuntu-image.rst:60 msgid "Select a mirror" msgstr "" #: ../ubuntu-image.rst:62 msgid "The default mirror proposed by the installer should be fine." msgstr "" #: ../ubuntu-image.rst:67 msgid "" "Step through the install, using the default options. When prompted for a " "user name, the default (``ubuntu``) is fine." msgstr "" #: ../ubuntu-image.rst:73 msgid "" "There are different options for partitioning the disks. The default " "installation will use LVM partitions, and will create three partitions (``/" "boot``, ``/``, swap), and this will work fine. Alternatively, you may wish " "to create a single ext4 partition, mounted to \"``/``\", should also work " "fine." msgstr "" #: ../ubuntu-image.rst:79 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 "" #: ../ubuntu-image.rst:83 msgid "Automatic updates" msgstr "" #: ../ubuntu-image.rst:85 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 "" #: ../ubuntu-image.rst:91 msgid "Software selection: OpenSSH server" msgstr "" #: ../ubuntu-image.rst:93 msgid "" "Choose :guilabel:`OpenSSH server` so that you will be able to SSH into the " "virtual machine when it launches inside of an OpenStack cloud." msgstr "" #: ../ubuntu-image.rst:99 msgid "Install GRUB boot loader" msgstr "" #: ../ubuntu-image.rst:101 msgid "" "Select :guilabel:`Yes` when asked about installing the GRUB boot loader to " "the master boot record." msgstr "" #: ../ubuntu-image.rst:107 msgid "" "For more information on configuring Grub, see the section called \":ref:" "`write-to-console`\"." msgstr "" #: ../ubuntu-image.rst:113 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 "" #: ../ubuntu-image.rst:121 msgid "" "There is a known bug in Ubuntu 14.04; when you select ``Continue``, the " "virtual machine will shut down, even though it says it will reboot." msgstr "" #: ../ubuntu-image.rst:124 msgid "" "To eject a disk using :command:`virsh`, libvirt requires that you attach an " "empty disk at the same target that the CDROM was previously attached, which " "should be ``hdc``. You can confirm the appropriate target using the :command:" "`virsh dumpxml vm-image` command." msgstr "" #: ../ubuntu-image.rst:145 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." msgstr "" #: ../ubuntu-image.rst:157 msgid "" "In the previous example, you paused the instance, ejected the disk, and " "unpaused the instance. In theory, you could have ejected the disk at the :" "guilabel:`Installation complete` screen. However, our testing indicates that " "the Ubuntu installer locks the drive so that it cannot be ejected at that " "point." msgstr "" #: ../ubuntu-image.rst:166 msgid "" "When you boot for the first time after install, it may ask you about " "authentication tools, you can just choose :guilabel:`Exit`. Then, log in as " "root using the root password you specified." msgstr "" #: ../ubuntu-image.rst:171 msgid "Install cloud-init" msgstr "" #: ../ubuntu-image.rst:173 msgid "" "The :command:`cloud-init` 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 "" #: ../ubuntu-image.rst:177 msgid "Install the ``cloud-init`` package:" msgstr "" #: ../ubuntu-image.rst:183 msgid "" "When building Ubuntu images :command:`cloud-init` 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 "" #: ../ubuntu-image.rst:188 msgid "" "To set the metadata source to be used by the image run the :command:`dpkg-" "reconfigure` command against the ``cloud-init`` package. When prompted " "select the :guilabel:`EC2` data source:" msgstr "" #: ../ubuntu-image.rst:200 msgid "" "You can change the name of the account used by cloud-init by editing the ``/" "etc/cloud/cloud.cfg`` 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:" msgstr "" #: ../ubuntu-image.rst:221 msgid "" "The operating system records the MAC address of the virtual Ethernet card in " "locations such as ``/etc/udev/rules.d/70-persistent-net.rules`` during the " "installation 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 "" #: ../ubuntu-image.rst:238 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 :" "command:`virsh undefine vm-image` command to inform libvirt:" msgstr "" #: ../ubuntu-image.rst:249 msgid "" "The underlying image file that you created with the :command:`qemu-img " "create` command, such as ``/tmp/trusty.qcow2``, is now ready for uploading " "to the Image service." msgstr "" #: ../virt-install.rst:3 msgid "Use virt-install and connect by using a local VNC client" msgstr "" #: ../virt-install.rst:5 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 :" "command:`virt-install` tool to boot the virtual machine through libvirt and " "connect to the graphical console from a VNC client installed on your local " "machine." msgstr "" #: ../virt-install.rst:12 msgid "" "Because VNC is a standard protocol, there are multiple clients available " "that implement the VNC spec, including `TigerVNC `_ (multiple " "platforms), `TightVNC `_ (multiple platforms), " "`RealVNC `_ (multiple platforms), `Chicken `_ (Mac OS X), `Krde `_ (KDE), `Vinagre `_ (GNOME)." msgstr "" #: ../virt-install.rst:22 msgid "" "The following example shows how to use the :command:`qemu-img` command to " "create an empty image file, and :command:`virt-install` command to start up " "a virtual machine using that image file. As root:" msgstr "" #: ../virt-install.rst:41 msgid "" "The KVM hypervisor starts the virtual machine with the libvirt name, " "``centos-6.4``, with 1024 MB of RAM. The virtual machine also has a virtual " "CD-ROM drive associated with the ``/data/CentOS-6.4-x86_64-netinstall.iso`` " "file and a local 10 GB hard disk in qcow2 format that is stored in the host " "at ``/data/centos-6.4.qcow2``. It configures networking to use libvirt " "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 (``--no-autoconsole``). Finally, libvirt will " "attempt to optimize the configuration for a Linux guest running a RHEL 6.x " "distribution." msgstr "" #: ../virt-install.rst:56 msgid "" "When using the libvirt ``default`` network, libvirt will connect the virtual " "machine's interface to a bridge called ``virbr0``. 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 "" #: ../virt-install.rst:63 msgid "" "Run the :command:`virt-install --os-variant list` command to see a range of " "allowed ``--os-variant`` options." msgstr "" #: ../virt-install.rst:66 msgid "" "Use the :command:`virsh vncdisplay vm-name` command to get the VNC port " "number." msgstr "" #: ../virt-install.rst:74 msgid "" "In the example above, the guest ``centos-6.4`` uses VNC display ``:1``, " "which corresponds to TCP port ``5901``. You should be able to connect a VNC " "client running on your local machine to display ``:1`` on the remote machine " "and step through the installation process." msgstr "" #: ../virt-manager.rst:3 msgid "Use the virt-manager X11 GUI" msgstr "" #: ../virt-manager.rst:5 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 :command:`virt-" "manager` GUI, which is installable as the ``virt-manager`` package on both " "Fedora-based and Debian-based systems. This GUI has an embedded VNC client " "that will let you view and interact with the guest's graphical console." msgstr "" #: ../virt-manager.rst:12 msgid "" "If you are building the image on a headless server, and you have an X server " "on your local machine, you can launch :command:`virt-manager` 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:" msgstr "" #: ../virt-manager.rst:23 msgid "" "If the account you use to ssh into your server does not have permissions to " "run libvirt, but has sudo privileges, do:" msgstr "" #: ../virt-manager.rst:33 msgid "" "The ``-X`` flag passed to ssh will enable X11 forwarding over ssh. If this " "does not work, try replacing it with the ``-Y`` flag." msgstr "" #: ../virt-manager.rst:36 msgid "" "Click the :guilabel:`New` button at the top-left and step through the " "instructions." msgstr "" #: ../virt-manager.rst:42 msgid "" "You will be shown a series of dialog boxes that will allow you to specify " "information about the virtual machine." msgstr "" #: ../virt-manager.rst:47 msgid "" "When using qcow2 format images you should check the option ``customize " "before install``, go to disk properties and explicitly select the :guilabel:" "`qcow2` format. This ensures the virtual machine disk size will be correct." msgstr "" #: ../windows-image.rst:3 msgid "Example: Microsoft Windows image" msgstr "" #: ../windows-image.rst:5 msgid "" "This example creates a Windows Server 2012 qcow2 image, using the :command:" "`virt-install` command and the KVM hypervisor." msgstr "" #: ../windows-image.rst:8 msgid "Follow these steps to prepare the installation:" msgstr "" #: ../windows-image.rst:10 msgid "" "Download a Windows Server 2012 installation ISO. Evaluation images are " "available on the `Microsoft website `_ (registration required)." msgstr "" #: ../windows-image.rst:14 msgid "" "Download the signed VirtIO drivers ISO from the `Fedora website `_." msgstr "" #: ../windows-image.rst:17 msgid "Create a 15 GB qcow2 image:" msgstr "" #: ../windows-image.rst:23 msgid "" "Start the Windows Server 2012 installation with the :command:`virt-install` " "command:" msgstr "" #: ../windows-image.rst:36 msgid "" "Use :command:`virt-manager` or :command:`virt-viewer` to connect to the VM " "and start the Windows installation." msgstr "" #: ../windows-image.rst:39 msgid "Enable the VirtIO drivers." msgstr "" #: ../windows-image.rst:41 msgid "" "The disk is not detected by default by the Windows installer. When requested " "to choose an installation target, click :guilabel:`Load driver` and browse " "the file system to select the ``E:\\WIN8\\AMD64`` folder. The Windows " "installer displays a list of drivers to install. Select the :guilabel:" "`VirtIO SCSI` and :guilabel:`network drivers` and continue the installation." msgstr "" #: ../windows-image.rst:48 msgid "" "Once the installation is completed, the VM restarts. Define a password for " "the administrator when prompted." msgstr "" #: ../windows-image.rst:51 msgid "Log in as administrator and start a command window." msgstr "" #: ../windows-image.rst:53 msgid "" "Complete the VirtIO drivers installation by running the following command:" msgstr "" #: ../windows-image.rst:60 msgid "" "To allow the :term:`Cloudbase-Init` to run scripts during an instance boot, " "set the PowerShell execution policy to be unrestricted:" msgstr "" #: ../windows-image.rst:68 msgid "Download and install the ``Cloudbase-Init``:" msgstr "" #: ../windows-image.rst:75 msgid "" "In the :guilabel:`configuration options` window, change the following " "settings:" msgstr "" #: ../windows-image.rst:78 msgid "Username: ``Administrator``" msgstr "" #: ../windows-image.rst:79 msgid "Network adapter to configure: ``Red Hat VirtIO Ethernet Adapter``" msgstr "" #: ../windows-image.rst:80 msgid "Serial port for logging: ``COM1``" msgstr "" #: ../windows-image.rst:82 msgid "" "When the installation is done, in the :guilabel:`Complete the Cloudbase-Init " "Setup Wizard` window, select the :guilabel:`Run Sysprep` and :guilabel:" "`Shutdown` check boxes and click :guilabel:`Finish`." msgstr "" #: ../windows-image.rst:87 msgid "Wait for the machine shutdown." msgstr "" #: ../windows-image.rst:89 msgid "Your image is ready to upload to the Image service:" msgstr ""