# # Translators: msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" "POT-Creation-Date: 2014-04-08 18:10+0000\n" "PO-Revision-Date: 2014-04-01 09:38+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: French (http://www.transifex.com/projects/p/openstack/language/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: fr\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" #: ./doc/image-guide/ch_modifying_images.xml10(title) msgid "Modify images" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml16(para) msgid "" "Do not attempt to use these tools to modify an image that is attached to a " "running virtual machine. These tools are designed to only modify images that" " are not currently running." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml12(para) msgid "" "Once you have obtained a virtual machine image, you may want to make some " "changes to it before uploading it to the OpenStack Image Service. Here we " "describe several tools available that allow you to modify " "images." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml22(title) msgid "guestfish" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml23(para) msgid "" "The program is a tool from the libguestfs project that allows you to" " modify the files inside of a virtual machine image." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml28(para) msgid "" " 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 commands, such as " ", , and , resemble " "traditional bash commands." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml38(title) msgid "Example guestfish session" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml39(para) msgid "" "Sometimes, you must modify a virtual machine image to remove any traces of " "the MAC address that was assigned to the virtual network interface card when" " the image was first created, because the MAC address will be different when" " it boots the next time. This example shows how to use guestfish to remove " "references to the old MAC address by deleting the " "/etc/udev/rules.d/70-persistent-net.rules file and " "removing the HWADDR line from the " "/etc/sysconfig/network-scripts/ifcfg-eth0 file." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml51(para) 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 "" #: ./doc/image-guide/ch_modifying_images.xml65(para) msgid "" "This starts a guestfish session. Note that the guestfish prompt looks like a" " fish: > <fs>." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml68(para) msgid "" "We must first use the 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. We " "can now view the file systems in the image using the " "command:We need to mount the logical volume that contains " "the root partition: " msgstr "" #: ./doc/image-guide/ch_modifying_images.xml82(para) msgid "" "Next, we want to delete a file. We can use the guestfish " "command, which works the same way it does in a traditional shell." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml86(para) msgid "" "We want to edit the ifcfg-eth0 file to " "remove the HWADDR line. The command will" " copy the file to the host, invoke your editor, and then copy the file back." " " msgstr "" #: ./doc/image-guide/ch_modifying_images.xml93(para) msgid "" "If you want to modify this image to load the 8021q kernel at boot time, you " "must create an executable script in the " "/etc/sysconfig/modules/ directory. You can use the " " guestfish command to create an empty file, the " " command to edit it, and the command to " "make it executable. We add the following line to the file " "and save it:Then we set to executable: " msgstr "" #: ./doc/image-guide/ch_modifying_images.xml107(para) msgid "" "We're done, so we can exit using the " "command:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml112(title) msgid "Go further with guestfish" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml113(para) msgid "" "There is an enormous amount of functionality in guestfish and a full " "treatment is beyond the scope of this document. Instead, we recommend that " "you read the guestfs-recipes documentation page for a sense of what is possible" " with these tools." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml123(title) msgid "guestmount" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml124(para) msgid "" "For some types of changes, you may find it easier to mount the image's file " "system directly in the guest. The program, also from the " "libguestfs project, allows you to do so." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml128(para) msgid "" "For example, to mount the root partition from our " "centos63_desktop.qcow2 image to " "/mnt, we can do:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml134(para) msgid "" "If we didn't 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:Once " "mounted, we could do things like list the installed packages using " "rpm: Once done, we unmount:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml146(title) msgid "virt-* tools" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml151(para) msgid "" "virt-edit for " "editing a file inside of an image." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml157(para) msgid "" "virt-df for " "displaying free space inside of an image." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml163(para) msgid "" "virt-resize " "for resizing an image." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml169(para) msgid "" "virt-sysprep" " for preparing an image for distribution (for example, delete SSH host keys," " remove MAC address info, or remove user accounts)." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml177(para) msgid "" "virt-" "sparsify for making an image sparse" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml183(para) msgid "" "virt-p2v for " "converting a physical machine to an image that runs on KVM" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml189(para) msgid "" "virt-v2v for " "converting Xen and VMWare images to KVM images" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml147(para) msgid "" "The libguestfs project has a " "number of other useful tools, including:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml196(title) msgid "Modify a single file inside of an image" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml197(para) msgid "" "This example shows how to use 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 "" #: ./doc/image-guide/ch_modifying_images.xml214(title) msgid "Resize an image" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml215(para) msgid "" "Here's a simple of example of how to use to resize an " "image. Assume we have a 16 GB Windows image in qcow2 format that we want to " "resize to 50 GB. First, we use to identify the " "partitions:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml227(para) msgid "" "In this case, it's the /dev/sda2 partition that we want" " to resize. We create a new qcow2 image and use the command" " to write a resized copy of the original into the new image: " "" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml261(title) msgid "Loop devices, kpartx, network block devices" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml265(para) msgid "" "Mounting untrusted guest images using the tools described in this section is" " a security risk, always use libguestfs tools such as guestfish and " "guestmount if you have access to them. See A reminder why you should " "never mount guest disk images on the host OS by Daniel Berrangé for " "more details." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml262(para) msgid "" "If you don't have access to libguestfs, you can mount image file systems " "directly in the host using loop devices, kpartx, and network block " "devices." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml275(title) msgid "Mount a raw image (without LVM)" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml276(para) msgid "" "If you have a raw virtual machine image that is not using LVM to manage its " "partitions. First, use the command to find an unused loop " "device. " msgstr "" #: ./doc/image-guide/ch_modifying_images.xml282(para) msgid "" "In this example, /dev/loop0 is free. Associate a loop " "device with the raw image:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml285(para) msgid "" "If the image only has a single partition, you can mount the loop device " "directly:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml288(para) msgid "" "If the image has multiple partitions, use to expose the " "partitions as separate devices (for example, " "/dev/mapper/loop0p1), then mount the partition that " "corresponds to the root file system:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml294(para) msgid "" "If the image has, say three partitions (/boot, /, /swap), there should be " "one new device created per partition:To mount the second " "partition, as root:Once you're done, to clean " "up:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml309(title) msgid "Mount a raw image (with LVM)" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml310(para) msgid "" "If your partitions are managed with LVM, use losetup and kpartx as in the " "previous example to expose the partitions to the host:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml317(para) msgid "" "Next, you need to use the command to identify the LVM " "volume groups and then to expose the volumes as devices:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml327(para) msgid "Clean up when you're done:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml334(title) msgid "Mount a qcow2 image (without LVM)" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml335(para) 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 "" #: ./doc/image-guide/ch_modifying_images.xml340(para) msgid "" "Assuming the first block device (/dev/nbd0) is not " "currently in use, we can expose the disk partitions using the " " and commands. As root:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml347(para) msgid "" "If the image has, say three partitions (/boot, /, /swap), there should be " "one new device created for each partition:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml356(para) msgid "" "If the network block device you selected was already in use, the initial " " command will fail silently, and the " "/dev/nbd3p{1,2,3} device files will not be created." msgstr "" #: ./doc/image-guide/ch_modifying_images.xml363(para) msgid "" "If the image partitions are not managed with LVM, they can be mounted " "directly:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml367(para) msgid "When you're done, clean up:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml372(title) msgid "Mount a qcow2 image (with LVM)" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml373(para) msgid "" "If the image partitions are managed with LVM, after you use " " and , you must use and in" " order to expose the LVM partitions as devices that can be " "mounted:" msgstr "" #: ./doc/image-guide/ch_modifying_images.xml387(para) msgid "When you're done, clean up:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_centos-example.xml80(None) #: ./doc/image-guide/section_centos-example.xml84(None) msgid "" "@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_centos-example.xml96(None) msgid "" "@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_centos-example.xml107(None) msgid "" "@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_centos-example.xml122(None) msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_centos-example.xml188(None) msgid "" "@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" msgstr "" #: ./doc/image-guide/section_centos-example.xml6(title) msgid "Example: CentOS image" msgstr "" #: ./doc/image-guide/section_centos-example.xml7(para) msgid "" "We'll run through an example of installing a CentOS image. This will focus " "mainly on CentOS 6.4. Because the CentOS installation process may change " "across versions, if you are using a different version of CentOS the " "installer steps may differ." msgstr "" #: ./doc/image-guide/section_centos-example.xml13(title) msgid "Download a CentOS install ISO" msgstr "" #: ./doc/image-guide/section_centos-example.xml17(para) msgid "" "Navigate to the CentOS " "mirrors page." msgstr "" #: ./doc/image-guide/section_centos-example.xml22(para) msgid "" "Click one of the HTTP links in the right-hand column next" " to one of the mirrors." msgstr "" #: ./doc/image-guide/section_centos-example.xml27(para) msgid "" "Click the folder link of the CentOS version you want to use. For example, " "6.4/." msgstr "" #: ./doc/image-guide/section_centos-example.xml32(para) msgid "Click the isos/ folder link." msgstr "" #: ./doc/image-guide/section_centos-example.xml36(para) msgid "Click the x86_64/ folder link for 64-bit images." msgstr "" #: ./doc/image-guide/section_centos-example.xml40(para) msgid "" "Click the ISO image you want to download. The netinstall ISO. For example, " "CentOS-6.4-x86_64-netinstall.iso is a good choice since" " it's a smaller image that will download missing packages from the Internet " "during the install process." msgstr "" #: ./doc/image-guide/section_centos-example.xml51(title) #: ./doc/image-guide/section_ubuntu-example.xml21(title) msgid "Start the install process" msgstr "" #: ./doc/image-guide/section_centos-example.xml52(para) #: ./doc/image-guide/section_ubuntu-example.xml22(para) msgid "" "Start the installation process using either or " " as described in the previous section. If using " ", don't forget to connect your VNC client to the virtual " "machine." msgstr "" #: ./doc/image-guide/section_centos-example.xml58(para) msgid "" "We will assume the name of your virtual machine image is " "centos-6.4, which we need to know when using " " commands to manipulate the state of the image." msgstr "" #: ./doc/image-guide/section_centos-example.xml62(para) #: ./doc/image-guide/section_ubuntu-example.xml32(para) msgid "" "If you're using virt-manager, the commands should look something like " "this:" msgstr "" #: ./doc/image-guide/section_centos-example.xml73(title) #: ./doc/image-guide/section_centos-example.xml174(title) #: ./doc/image-guide/section_ubuntu-example.xml43(title) #: ./doc/image-guide/section_ubuntu-example.xml69(title) msgid "Step through the install" msgstr "" #: ./doc/image-guide/section_centos-example.xml74(para) msgid "" "At the initial Installer boot menu, choose the \"Install or upgrade an " "existing system\" option. Step through the install prompts, the defaults " "should be fine." msgstr "" #: ./doc/image-guide/section_centos-example.xml89(title) msgid "Configure TCP/IP" msgstr "" #: ./doc/image-guide/section_centos-example.xml90(para) msgid "" "The default TCP/IP settings are fine. In particular, ensure that Enable IPv4" " support is enabled with DHCP, which is the default." msgstr "" #: ./doc/image-guide/section_centos-example.xml102(title) msgid "Point the installer to a CentOS web server" msgstr "" #: ./doc/image-guide/section_centos-example.xml103(para) msgid "Choose URL as the installation method." msgstr "" #: ./doc/image-guide/section_centos-example.xml116(para) msgid "Consider using other mirrors as an alternative to mirror.umd.edu." msgstr "" #: ./doc/image-guide/section_centos-example.xml110(para) msgid "" "Depending on the version of CentOS, the net installer requires that the user" " specify either a URL, or the web site and a CentOS directory that " "corresponds to one of the CentOS mirrors. If the installer asks for a single" " URL, an example of a valid URL would be: " "http://mirror.umd/centos/6/os/x86_64." msgstr "" #: ./doc/image-guide/section_centos-example.xml126(para) msgid "" "If the installer asks for web site name and CentOS directory separately, an " "example would be:" msgstr "" #: ./doc/image-guide/section_centos-example.xml131(para) msgid "Web site name: mirror.umd.edu" msgstr "" #: ./doc/image-guide/section_centos-example.xml136(para) msgid "CentOS directory: centos/6/os/x86_64" msgstr "" #: ./doc/image-guide/section_centos-example.xml141(para) 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 "" #: ./doc/image-guide/section_centos-example.xml148(title) msgid "Storage devices" msgstr "" #: ./doc/image-guide/section_centos-example.xml149(para) msgid "" "If asked about what type of devices your installation involves, choose " "\"Basic Storage Devices\"." msgstr "" #: ./doc/image-guide/section_centos-example.xml153(title) #: ./doc/image-guide/section_ubuntu-example.xml55(title) msgid "Hostname" msgstr "Nom d'Hôte" #: ./doc/image-guide/section_centos-example.xml154(para) msgid "" "The installer may ask you to choose a hostname. The default " "(localhost.localdomain) is fine. We will install the " "cloud-init package later, which will set the hostname on boot when a new " "instance is provisioned using this image." msgstr "" #: ./doc/image-guide/section_centos-example.xml161(title) #: ./doc/image-guide/section_ubuntu-example.xml75(title) msgid "Partition the disks" msgstr "" #: ./doc/image-guide/section_centos-example.xml162(para) #: ./doc/image-guide/section_ubuntu-example.xml76(para) 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 "" #: ./doc/image-guide/section_centos-example.xml169(para) #: ./doc/image-guide/section_ubuntu-example.xml83(para) msgid "" "If unsure, we recommend you use the installer's default partition scheme, " "since there is no clear advantage to one scheme or another." msgstr "" #: ./doc/image-guide/section_centos-example.xml175(para) msgid "" "Step through the install, using the default options. The simplest thing to " "do is to choose the \"Basic Server\" install (may be called \"Server\" " "install on older versions of CentOS), which will install an SSH server." msgstr "" #: ./doc/image-guide/section_centos-example.xml181(title) #: ./doc/image-guide/section_ubuntu-example.xml120(title) msgid "Detach the CD-ROM and reboot" msgstr "" #: ./doc/image-guide/section_centos-example.xml182(para) msgid "" "Once the install completes, you will see the screen \"Congratulations, your " "CentOS installation is complete\"." msgstr "" #: ./doc/image-guide/section_centos-example.xml197(replaceable) #: ./doc/image-guide/section_centos-example.xml374(replaceable) #: ./doc/image-guide/section_ubuntu-example.xml144(replaceable) #: ./doc/image-guide/section_ubuntu-example.xml238(replaceable) msgid "vm-image" msgstr "" #: ./doc/image-guide/section_centos-example.xml192(para) #: ./doc/image-guide/section_ubuntu-example.xml139(para) msgid "" "To eject a disk using , 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." msgstr "" #: ./doc/image-guide/section_centos-example.xml212(para) msgid "" "Run the following commands from the host to eject the disk and reboot using " "virsh, as root. If you are using virt-manager, the commands below will work," " but you can also use the GUI to detach and reboot it by manually stopping " "and starting." msgstr "" #: ./doc/image-guide/section_centos-example.xml221(para) msgid "" "In theory, the command can be used instead of using destroy" " and start commands. However, in our testing we were unable to reboot " "successfully using the command." msgstr "" #: ./doc/image-guide/section_centos-example.xml230(title) #: ./doc/image-guide/section_ubuntu-example.xml176(title) msgid "Log in to newly created image" msgstr "" #: ./doc/image-guide/section_centos-example.xml231(para) msgid "" "When you boot for the first time after install, it may ask you about " "authentication tools, you can just choose \"Exit\". Then, log in as root " "using the root password you specified." msgstr "" #: ./doc/image-guide/section_centos-example.xml237(title) msgid "Configure to fetch metadata" msgstr "" #: ./doc/image-guide/section_centos-example.xml243(para) msgid "" "Install a cloud-init RPM, which is a port of the Ubuntu cloud-init package. This is" " the recommended approach." msgstr "" #: ./doc/image-guide/section_centos-example.xml250(para) msgid "" "Modify /etc/rc.local to fetch desired information from " "the metadata service, as described below." msgstr "" #: ./doc/image-guide/section_centos-example.xml238(para) msgid "" "An instance must perform several steps on start up by interacting with the " "metadata service. For example, retrieve ssh public key and execute user data" " script. There are several ways to implement this functionality, " "including:" msgstr "" #: ./doc/image-guide/section_centos-example.xml257(title) msgid "Use cloud-init to fetch the public key" msgstr "" #: ./doc/image-guide/section_centos-example.xml258(para) msgid "" "The cloud-init package will automatically fetch the public key from the " "metadata server and place the key in an account. You can install cloud-init " "inside the CentOS guest by adding the EPEL repo:" msgstr "" #: ./doc/image-guide/section_centos-example.xml264(para) #: ./doc/image-guide/section_ubuntu-example.xml201(para) msgid "" "The account varies by distribution. On Ubuntu-based virtual machines, the " "account is called \"ubuntu\". On Fedora-based virtual machines, the account " "is called \"ec2-user\"." msgstr "" #: ./doc/image-guide/section_centos-example.xml268(para) 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 "" #: ./doc/image-guide/section_centos-example.xml278(title) msgid "Write a script to fetch the public key (if no cloud-init)" msgstr "" #: ./doc/image-guide/section_centos-example.xml280(para) msgid "" "If you are not able to install the cloud-init package in your image, to " "fetch the ssh public key and add it to the root account, edit the " "/etc/rc.local file and add the following lines before " "the line “touch /var/lock/subsys/local”" msgstr "" #: ./doc/image-guide/section_centos-example.xml310(para) msgid "" "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) " "with - (hyphen). Make sure it's http: not http; and authorized_keys not " "authorized-keys." msgstr "" #: ./doc/image-guide/section_centos-example.xml316(para) msgid "" "The above script only retrieves the ssh public key from the metadata server." " It does not retrieve user data, which " "is optional data that can be passed by the user when requesting a new " "instance. User data is often used for running a custom script when an " "instance comes up." msgstr "" #: ./doc/image-guide/section_centos-example.xml323(para) msgid "" "As the OpenStack metadata service is compatible with version 2009-04-04 of " "the Amazon EC2 metadata service, consult the Amazon EC2 documentation on " "Using Instance Metadata for " "details on how to retrieve user data." msgstr "" #: ./doc/image-guide/section_centos-example.xml332(title) msgid "Disable the zeroconf route" msgstr "" #: ./doc/image-guide/section_centos-example.xml333(para) msgid "" "In order for the instance to access the metadata service, disable the " "default zeroconf route:" msgstr "" #: ./doc/image-guide/section_centos-example.xml338(title) msgid "Configure console" msgstr "" #: ./doc/image-guide/section_centos-example.xml345(replaceable) msgid "..." msgstr "" #: ./doc/image-guide/section_centos-example.xml339(para) msgid "" "In order for to work properly on CentOS 6.x, guests you may" " need to add the following lines to " "/boot/grub/menu.lst" msgstr "" #: ./doc/image-guide/section_centos-example.xml348(title) #: ./doc/image-guide/section_ubuntu-example.xml214(title) msgid "Shut down the instance" msgstr "" #: ./doc/image-guide/section_centos-example.xml349(para) #: ./doc/image-guide/section_ubuntu-example.xml215(para) msgid "From inside the instance, as root:" msgstr "" #: ./doc/image-guide/section_centos-example.xml353(title) #: ./doc/image-guide/section_ubuntu-example.xml219(title) msgid "Clean up (remove MAC address details)" msgstr "" #: ./doc/image-guide/section_centos-example.xml354(para) 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 "" #: ./doc/image-guide/section_centos-example.xml363(para) #: ./doc/image-guide/section_ubuntu-example.xml227(para) msgid "" "There is a utility called , that performs various cleanup " "tasks such as removing the MAC address references. It will clean up a " "virtual machine image in place:" msgstr "" #: ./doc/image-guide/section_centos-example.xml370(title) #: ./doc/image-guide/section_ubuntu-example.xml234(title) msgid "Undefine the libvirt domain" msgstr "" #: ./doc/image-guide/section_centos-example.xml371(para) msgid "" "Now that the image is ready to be uploaded to the Image Service, you no " "longer need to have this virtual machine image managed by libvirt. Use the " " command to inform libvirt." msgstr "" #: ./doc/image-guide/section_centos-example.xml379(title) #: ./doc/image-guide/section_ubuntu-example.xml243(title) msgid "Image is complete" msgstr "" #: ./doc/image-guide/section_centos-example.xml380(para) msgid "" "The underlying image file you created with . For example, " "/tmp/centos-6.4.qcow2 is now ready for uploading to the" " OpenStack Image Service." msgstr "" #: ./doc/image-guide/bk-imageguide.xml10(title) msgid "OpenStack Virtual Machine Image Guide" msgstr "" #: ./doc/image-guide/bk-imageguide.xml12(titleabbrev) msgid "VM Image Guide" msgstr "" #: ./doc/image-guide/bk-imageguide.xml20(orgname) #: ./doc/image-guide/bk-imageguide.xml25(holder) msgid "OpenStack Foundation" msgstr "Fondation OpenStack" #: ./doc/image-guide/bk-imageguide.xml24(year) msgid "2013" msgstr "2013" #: ./doc/image-guide/bk-imageguide.xml27(releaseinfo) msgid "havana" msgstr "havana" #: ./doc/image-guide/bk-imageguide.xml28(productname) msgid "OpenStack" msgstr "OpenStack" #: ./doc/image-guide/bk-imageguide.xml32(remark) msgid "Remaining licensing details are filled in by the template." msgstr "Les détails supplémentaires concernant la licence sont intégrés dans le modèle de document." #: ./doc/image-guide/bk-imageguide.xml37(para) msgid "" "This guide describes how to obtain, create, and modify virtual machine " "images that are compatible with OpenStack." msgstr "" #: ./doc/image-guide/bk-imageguide.xml44(date) msgid "2013-10-25" msgstr "" #: ./doc/image-guide/bk-imageguide.xml48(para) msgid "Adds information about image formats, properties." msgstr "" #: ./doc/image-guide/bk-imageguide.xml54(date) msgid "2013-10-17" msgstr "17-10-2013" #: ./doc/image-guide/bk-imageguide.xml58(para) msgid "Havana release." msgstr "Havana lancement." #: ./doc/image-guide/bk-imageguide.xml64(date) msgid "2013-06-04" msgstr "" #: ./doc/image-guide/bk-imageguide.xml68(para) msgid "Updated title for consistency." msgstr "" #: ./doc/image-guide/bk-imageguide.xml74(date) msgid "2013-05-28" msgstr "" #: ./doc/image-guide/bk-imageguide.xml78(para) msgid "Initial release of this guide." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_ubuntu-example.xml50(None) msgid "" "@@image: 'figures/ubuntu-install.png'; md5=a1f2ab707b7bc3122e20e6e0e4580887" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_ubuntu-example.xml104(None) msgid "" "@@image: 'figures/ubuntu-software-selection.png'; " "md5=423be828f701345f7d20551a39f24271" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_ubuntu-example.xml115(None) msgid "" "@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/section_ubuntu-example.xml128(None) msgid "" "@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml6(title) msgid "Example: Ubuntu image" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml7(para) msgid "" "We'll run through an example of installing an Ubuntu image. This will focus " "mainly on Ubuntu 12.04 (Precise Pangolin) server. Because the Ubuntu " "installation process may change across versions, if you are using a " "different version of Ubuntu the installer steps may differ." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml13(title) msgid "Download an Ubuntu install ISO" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml14(para) msgid "" "In this example, we'll use the network installation ISO, since it's a " "smaller image. The 64-bit 12.04 network installer ISO is at http://archive.ubuntu.com/ubuntu/dists/precise/main" "/installer-amd64/current/images/netboot/mini.iso" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml28(para) msgid "" "We will assume the name of your virtual machine image is " "ubuntu-12.04, which we need to know when using " " commands to manipulate the state of the image." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml44(para) msgid "" "At the initial Installer boot menu, choose the \"Install\" option. Step " "through the install prompts, the defaults should be fine." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml56(para) msgid "" "The installer may ask you to choose a hostname. The default " "(ubuntu) is fine. We will install the cloud-init package " "later, which will set the hostname on boot when a new instance is " "provisioned using this image." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml64(title) msgid "Select a mirror" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml65(para) msgid "The default mirror proposed by the installer should be fine." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml70(para) msgid "" "Step through the install, using the default options. When prompted for a " "username, the default (ubuntu) is fine." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml88(title) msgid "Automatic updates" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml89(para) msgid "" "The Ubuntu installer will ask how you want to manage upgrades on your " "system. This option depends on your specific use case. If your virtual " "machine instances will be connected to the internet, we recommend \"Install " "security updates automatically\"." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml96(title) msgid "Software selection: OpenSSH server" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml97(para) msgid "" "Choose \"OpenSSH server\"so that you will be able to SSH into the virtual " "machine when it launches inside of an OpenStack cloud." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml109(title) msgid "Install GRUB boot loader" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml110(para) msgid "" "Select \"Yes\" when asked about installing the GRUB boot loader to the " "master boot record." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml121(para) msgid "" "Select the defaults for all of the remaining options. When the installation " "is complete, you will be prompted to remove the CD-ROM." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml133(para) msgid "" "When you hit \"Continue\" the virtual machine will shut down, even though it" " says it will reboot." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml160(para) msgid "" "Run the following commands in the host as root to start up the machine again" " as paused, eject the disk and resume. If you are using virt-manager, you " "may use the GUI instead." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml167(para) msgid "" "In the example above, we start the instance paused, eject the disk, and then" " unpause. In theory, we could have ejected the disk at the \"Installation " "complete\" screen. However, our testing indicates that the Ubuntu installer " "locks the drive so that it cannot be ejected at that point." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml177(para) msgid "" "When you boot for the first time after install, it may ask you about " "authentication tools, you can just choose 'Exit'. Then, log in as root using" " the root password you specified." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml183(title) msgid "Install cloud-init" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml184(para) msgid "" "The script starts on instance boot and will search for a " "metadata provider to fetch a public key from. The public key will be placed " "in the default user account for the image." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml188(para) msgid "Install the cloud-init package:" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml190(para) msgid "" "When building Ubuntu images must be explicitly configured " "for the metadata source in use. The OpenStack metadata server emulates the " "EC2 metadata service used by images in Amazon EC2." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml195(para) msgid "" "To set the metadata source to be used by the image run the " "command against the cloud-init package. When prompted " "select the EC2 data source: " msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml205(para) 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 "" #: ./doc/image-guide/section_ubuntu-example.xml220(para) 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 instance process. However, each time the " "image boots up, the virtual ethernet card will have a different MAC address," " so this information must be deleted from the configuration file." msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml235(para) msgid "" "Now that the image is ready to be uploaded to the Image Service, we no " "longer need to have this virtual machine image managed by libvirt. Use the " " command to inform libvirt" msgstr "" #: ./doc/image-guide/section_ubuntu-example.xml244(para) msgid "" "The underlying image file that you created with , such as " "/tmp/precise.qcow2, is now ready for uploading to the " "OpenStack Image Service." msgstr "" #: ./doc/image-guide/ch_introduction.xml6(title) msgid "Introduction" msgstr "Introduction" #: ./doc/image-guide/ch_introduction.xml7(para) msgid "" "An OpenStack Compute cloud is not very useful unless you have virtual " "machine images (which some people call \"virtual appliances\"). This guide " "describes how to obtain, create, and modify virtual machine images that are " "compatible with OpenStack." msgstr "" #: ./doc/image-guide/ch_introduction.xml10(para) msgid "" "To keep things brief, we'll sometimes use the term \"image\" instead of " "\"virtual machine image\"." msgstr "" #: ./doc/image-guide/ch_introduction.xml12(para) msgid "What is a virtual machine image?" msgstr "" #: ./doc/image-guide/ch_introduction.xml13(para) msgid "" "A virtual machine image is a single file which contains a virtual disk that " "has a bootable operating system installed on it." msgstr "" #: ./doc/image-guide/ch_introduction.xml15(para) msgid "" "Virtual machine images come in different formats, some of which are " "described below. In a later chapter, we'll describe how to convert between " "formats." msgstr "" #: ./doc/image-guide/ch_introduction.xml19(term) msgid "Raw" msgstr "Raw" #: ./doc/image-guide/ch_introduction.xml26(para) msgid "" "We don't recommend creating raw images by dd'ing block device files, we " "discuss how to create raw images later." msgstr "" #: ./doc/image-guide/ch_introduction.xml20(para) msgid "" "The \"raw\" image format is the simplest one, and is natively supported by " "both KVM and Xen hypervisors. You can think of a raw image as being the bit-" "equivalent of a block device file, created as if somebody had copied, say, " "/dev/sda to a file using the command. " "" msgstr "" #: ./doc/image-guide/ch_introduction.xml32(term) #: ./doc/image-guide/ch_converting.xml26(td) #: ./doc/image-guide/ch_converting.xml27(literal) msgid "qcow2" msgstr "" #: ./doc/image-guide/ch_introduction.xml37(para) msgid "Using sparse representation, so the image size is smaller" msgstr "" #: ./doc/image-guide/ch_introduction.xml40(para) msgid "Support for snapshots" msgstr "" #: ./doc/image-guide/ch_introduction.xml33(para) 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 "" #: ./doc/image-guide/ch_introduction.xml43(para) msgid "" "Because qcow2 is sparse, it's often faster to convert a raw image to qcow2 " "and upload it then to upload the raw file." msgstr "" #: ./doc/image-guide/ch_introduction.xml47(para) msgid "" "Because raw images don't support snapshots, OpenStack Compute will " "automatically convert raw image files to qcow2 as needed." msgstr "" #: ./doc/image-guide/ch_introduction.xml53(term) msgid "AMI/AKI/ARI" msgstr "" #: ./doc/image-guide/ch_introduction.xml59(para) msgid "AMI (Amazon Machine Image):" msgstr "" #: ./doc/image-guide/ch_introduction.xml60(para) msgid "This is a virtual machine image in raw format, as described above." msgstr "" #: ./doc/image-guide/ch_introduction.xml64(para) msgid "AKI (Amazon Kernel Image)" msgstr "" #: ./doc/image-guide/ch_introduction.xml65(para) 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 "" #: ./doc/image-guide/ch_introduction.xml72(para) msgid "ARI (Amazon Ramdisk Image)" msgstr "" #: ./doc/image-guide/ch_introduction.xml73(para) msgid "" "An optional ramdisk file mounted at boot time. For a Linux machine, this " "would be an initrd file." msgstr "" #: ./doc/image-guide/ch_introduction.xml54(para) msgid "" "The AMI/AKI/ARI" " format was the initial image format supported by Amazon EC2. The " "image consists of three files:" msgstr "" #: ./doc/image-guide/ch_introduction.xml81(term) msgid "UEC tarball" msgstr "" #: ./doc/image-guide/ch_introduction.xml84(para) msgid "" "Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu " "cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud " "Infrastructure." msgstr "" #: ./doc/image-guide/ch_introduction.xml82(para) msgid "" "A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains " "an AMI file, AKI file, and ARI file." msgstr "" #: ./doc/image-guide/ch_introduction.xml90(term) msgid "VMDK" msgstr "VMDK" #: ./doc/image-guide/ch_introduction.xml91(para) msgid "" "VMWare's ESXi hypervisor uses the VMDK (Virtual Machine " "Disk) format for images." msgstr "" #: ./doc/image-guide/ch_introduction.xml96(term) msgid "VDI" msgstr "VDI" #: ./doc/image-guide/ch_introduction.xml97(para) 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 "" #: ./doc/image-guide/ch_introduction.xml104(term) msgid "VHD" msgstr "VHD" #: ./doc/image-guide/ch_introduction.xml105(para) msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." msgstr "" #: ./doc/image-guide/ch_introduction.xml108(term) msgid "VHDX" msgstr "" #: ./doc/image-guide/ch_introduction.xml109(para) 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 "" #: ./doc/image-guide/ch_introduction.xml115(term) msgid "OVF" msgstr "" #: ./doc/image-guide/ch_introduction.xml116(para) 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 "" #: ./doc/image-guide/ch_introduction.xml121(para) msgid "" "An OVF package can be distributed in different ways. For example, it could " "be distributed as a set of discrete files, or as a tar archive file with an " ".ova (open virtual appliance/application) extension." msgstr "" #: ./doc/image-guide/ch_introduction.xml124(para) msgid "" "OpenStack Compute does not currently have support for OVF packages, so you " "will need to extract the image file(s) from an OVF package if you wish to " "use it with OpenStack." msgstr "" #: ./doc/image-guide/ch_introduction.xml129(term) msgid "ISO" msgstr "" #: ./doc/image-guide/ch_introduction.xml130(para) 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 don't normally think of" " ISO as a virtual machine image format, since ISOs contain bootable " "filesystems with an installed operating system, you can treat them the same " "as you treat other virtual machine image files." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml6(title) msgid "Tool support for image creation" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml8(para) msgid "There are several tools that are designed to automate image creation." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml11(title) msgid "Oz" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml22(para) msgid "" "As of this writing, there are no Oz packages for Ubuntu, so you will need to" " either install from source or build your own .deb file." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml12(para) 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 "" #: ./doc/image-guide/ch_creating_images_automatically.xml26(para) msgid "" "A full treatment of Oz is beyond the scope of this document, but we will " "provide an example. You can find additional examples of Oz template files on" " github at rackerjoe/oz-image-build/templates. " "Here's how you would create a CentOS 6.4 image with Oz." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml33(para) 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 " "<rootpw> contents." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml71(para) msgid "" "This Oz template specifies where to download the Centos 6.4 install ISO. Oz " "will use the version information to identify which kickstart file to use. In" " this case, it will be 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 "" #: ./doc/image-guide/ch_creating_images_automatically.xml82(para) msgid "" "After Oz does the initial OS install using the kickstart file, it customizes" " the image by doing an update. It also removes any reference to the eth0 " "device that libvirt creates while Oz does the customizing, as specified in " "the command section of the XML file." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml88(para) msgid "To run this, do, as root:" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml91(para) msgid "" "The -d3 flag tells Oz to show status information as it " "runs." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml95(para) msgid "" "The -u tells Oz to do the customization (install extra " "packages, run the commands) once it does the initial install." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml101(para) msgid "" "The -x <filename> 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 "" #: ./doc/image-guide/ch_creating_images_automatically.xml89(para) msgid "" "If you leave out the -u " "flag, or you want to edit the file to do additional customizations, you can " "use the command, using the libvirt XML file that " " creates. For example: Oz will invoke " "libvirt to boot the image inside of KVM, then Oz will ssh into the instance " "and perform the customizations." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml119(title) msgid "VMBuilder" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml120(para) 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 "" #: ./doc/image-guide/ch_creating_images_automatically.xml127(para) msgid "" "The Ubuntu Server Guide has " "documentation on how to use VMBuilder to create an Ubuntu image." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml134(title) msgid "BoxGrinder" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml135(para) msgid "" "BoxGrinder  is another tool for" " creating virtual machine images, which it calls appliances. BoxGrinder can " "create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is " "currently only supported on Fedora." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml144(title) msgid "VeeWee" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml145(para) msgid "" " VeeWee is often " "used to build Vagrant boxes, but " "it can also be used to build KVM images." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml151(title) msgid "imagefactory" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml152(para) 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 "" #: ./doc/image-guide/ch_creating_images_automatically.xml159(title) msgid "SUSE Studio" msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml160(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml10(title) msgid "OpenStack Linux image requirements" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml12(para) msgid "" "For a Linux-based image to have full functionality in an OpenStack Compute " "cloud, there are a few requirements. For some of these, you can fulfill the " "requirement by installing the 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 "" #: ./doc/image-guide/ch_openstack_images.xml22(para) msgid "" "Disk partitions and resize root partition on boot (cloud-" "init)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml26(para) #: ./doc/image-guide/ch_openstack_images.xml234(title) msgid "No hard-coded MAC address information" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml29(para) msgid "SSH server running" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml32(para) #: ./doc/image-guide/ch_openstack_images.xml278(title) msgid "Disable firewall" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml35(para) msgid "Access instance using ssh public key (cloud-init)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml39(para) msgid "Process user data and other metadata (cloud-init)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml43(para) msgid "" "Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux " "kernel version < 3.0)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml49(title) msgid "Disk partitions and resize root partition on boot (cloud-init)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml51(para) msgid "" "When you create a Linux image, you must decide how to partition the disks. " "The choice of partition method can affect the resizing functionality, as " "described in the following sections." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml55(para) msgid "" "The size of the disk in a virtual machine image is determined when you " "initially create the image. However, OpenStack lets you launch instances " "with different size drives by specifying different flavors. For example, if " "your image was created with a 5 GB disk, and you launch an instance with a " "flavor of 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 "" #: ./doc/image-guide/ch_openstack_images.xml65(para) msgid "" "Your image must be able to resize its partitions on boot to match the size " "requested by the user. Otherwise, after the instance boots, you must " "manually resize the partitions to access the additional storage to which you" " have access when the disk size associated with the flavor exceeds the disk " "size with which your image was created." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml73(title) msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml75(para) msgid "" "If you use the OpenStack XenAPI driver, the Compute service automatically " "adjusts the partition and file system for your instance on boot. Automatic " "resize occurs if the following conditions are all true:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml82(para) msgid "" "auto_disk_config=True is set as a property on the image " "in the image registry." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml87(para) msgid "The disk on the image has only one partition." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml91(para) msgid "The file system on the one partition is ext3 or ext4." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml95(para) msgid "" "Therefore, if you use Xen, we recommend that when you create your images, " "you create a single ext3 or ext4 partition (not managed by LVM). Otherwise, " "read on." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml101(title) msgid "" "Non-Xen with cloud-init/cloud-tools: One ext3/ext4 partition (no LVM, no " "/boot, no swap)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml103(para) msgid "You must configure these items for your image:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml107(para) msgid "" "The partition table for the image describes the original size of the image" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml111(para) msgid "The file system for the image fills the original size of the image" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml115(para) msgid "Then, during the boot process, you must:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml118(para) msgid "Modify the partition table to make it aware of the additional space:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml122(para) msgid "" "If you do not use LVM, you must modify the table to extend the existing root" " partition to encompass this additional space." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml128(para) msgid "" "If you use LVM, you can add a new LVM entry to the partition table, create a" " new LVM physical volume, add it to the volume group, and extend the logical" " partition with the root volume." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml138(para) msgid "Resize the root volume file system." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml141(para) msgid "" "The simplest way to support this in your image is to install the cloud-utils package " "(contains the tool for extending partitions), the cloud-initramfs-" "tools package (which supports resizing root partition on the first " "boot), and the cloud-init package into your image. With these 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 "" #: ./doc/image-guide/ch_openstack_images.xml160(para) 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 " " so that the image resizes properly on boot." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml168(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml175(title) msgid "" "Non-Xen without cloud-init/cloud-" "tools: LVM" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml178(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml189(para) msgid "" "Detect if any additional space is available on the disk. For example, parse " "the output of ." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml196(para) msgid "" "Create a new LVM partition with the additional space. For example, " "." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml204(replaceable) #: ./doc/image-guide/ch_openstack_images.xml211(replaceable) #: ./doc/image-guide/ch_openstack_images.xml218(replaceable) msgid "sda6" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml202(para) msgid "Create a new physical volume. For example, ." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml210(replaceable) msgid "vg00" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml207(para) msgid "" "Extend the volume group with this physical partition. For example, " ".)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml217(replaceable) #: ./doc/image-guide/ch_openstack_images.xml223(replaceable) msgid "node-root" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml214(para) msgid "" "Extend the logical volume contained the root partition by the amount of " "space. For example, ." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml221(para) msgid "Resize the root file system. For example, ." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml187(para) msgid "Your script must do something like the following:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml226(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml235(para) msgid "" "You must remove the network persistence rules in the image because they " "cause the network interface in the instance to come up as an interface other" " than eth0. This is because your image has a record of the MAC address of " "the network interface card when it was first installed, and this MAC address" " is different each time that the instance boots. You should alter the " "following files:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml245(para) msgid "" "Replace /etc/udev/rules.d/70-persistent-net.rules with " "an empty file (contains network persistence rules, including MAC address)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml251(para) msgid "" "Replace /lib/udev/rules.d/75-persistent-net-" "generator.rules with an empty file (this generates the file " "above)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml257(para) msgid "" "Remove the HWADDR line from /etc/sysconfig/network-scripts/ifcfg-" "eth0 on Fedora-based images" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml263(para) msgid "" "If you delete the network persistent rules files, you may get a udev kernel " "warning at boot time, which is why we recommend replacing them with empty " "files instead." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml270(title) msgid "Ensure ssh server runs" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml271(para) msgid "" "You must install an ssh server into the image and ensure that it starts up " "on boot, or you cannot connect to your instance by using ssh when it boots " "inside of OpenStack. This package is typically called openssh-" "server." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml279(para) msgid "" "In general, we recommend that you disable any firewalls inside of your image" " and use OpenStack security groups to restrict access to instances. The " "reason is that having a firewall installed on your instance can make it more" " difficult to troubleshoot networking issues if you cannot connect to your " "instance." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml287(title) msgid "Access instance by using ssh public key (cloud-init)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml289(para) msgid "" "The typical way that users access virtual machines running on OpenStack is " "to ssh using public key authentication. For this to work, your virtual " "machine image must be configured to download the ssh public key from the " "OpenStack metadata service or config drive, at boot time." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml296(title) msgid "Use cloud-init to fetch the public key" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml298(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml306(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml316(title) msgid "Write a custom script to fetch the public key" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml318(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml322(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml362(para) msgid "" "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) " "with - (hyphen). If editing a file over a VNC session, make sure it's http: " "not http; and authorized_keys not authorized-keys." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml374(title) msgid "Process user data and other metadata (cloud-init)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml376(para) msgid "" "In addition to the ssh public key, an image might need additional " "information from OpenStack, such as user data that the user " "submitted when requesting the image. For example, you might want to set the " "host name of the instance when it is booted. Or, you might wish to configure" " your image so that it executes user data content as a script on boot." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml384(para) msgid "" "This information is accessible through the metadata service or the config 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 user data." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml395(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml402(title) msgid "Ensure image writes boot log to console" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml403(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml407(para) 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 "" #: ./doc/image-guide/ch_openstack_images.xml412(para) 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 /etc/default/grub and modify " "the value of the GRUB_CMDLINE_LINUX_DEFAULT variable: " "" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml421(para) msgid "" "Next, update the grub configuration. On Debian-based operating-systems such " "as Ubuntu, run this command:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml424(para) msgid "" "On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this " "command:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml429(title) msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml431(para) msgid "" "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel " "did not have support paravirtualized Xen virtual machine instances (what Xen" " calls DomU guests). If you are running the Xen hypervisor with " "paravirtualization, and you want to create an image for an older Linux " "distribution that has a pre 3.0 kernel, you must ensure that the image boots" " a kernel that has been compiled with Xen support." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml441(title) msgid "Manage the image cache" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml442(para) msgid "" "Use options in nova.conf to control whether, and for " "how long, unused base images are stored in " "/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 "" #: ./doc/image-guide/ch_openstack_images.xml449(para) msgid "" "For information about libvirt images in OpenStack, see The life of" " an OpenStack libvirt image from Pádraig Brady." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml455(caption) msgid "Image cache management configuration options" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml461(td) msgid "Configuration option=Default value" msgstr "Option de configuration=Valeur par défaut" #: ./doc/image-guide/ch_openstack_images.xml462(td) msgid "(Type) Description" msgstr "(Type) Description" #: ./doc/image-guide/ch_openstack_images.xml467(td) msgid "preallocate_images=none" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml468(para) msgid "(StrOpt) VM image preallocation mode:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml471(para) msgid "none. No storage provisioning occurs up front." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml476(para) msgid "" "space. 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 "" #: ./doc/image-guide/ch_openstack_images.xml493(td) msgid "remove_unused_base_images=True" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml494(td) msgid "" "(BoolOpt) Should unused base images be removed? When set to True, the " "interval at which base images are removed are set with the following two " "settings. If set to False base images are never removed by Compute." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml501(td) msgid "remove_unused_original_minimum_age_seconds=86400" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml502(td) msgid "" "(IntOpt) Unused unresized base images younger than this are not removed. " "Default is 86400 seconds, or 24 hours." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml507(td) msgid "remove_unused_resized_minimum_age_seconds=3600" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml508(td) msgid "" "(IntOpt) Unused resized base images younger than this are not removed. " "Default is 3600 seconds, or one hour." msgstr "" #: ./doc/image-guide/ch_openstack_images.xml514(para) msgid "" "To see how the settings affect the deletion of a running instance, check the" " directory where the images are stored:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml518(para) msgid "" "In the /var/log/compute/compute.log file, look for the " "identifier:" msgstr "" #: ./doc/image-guide/ch_openstack_images.xml525(para) 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 nova.conf. Restart " "all nova services after changing a setting in " "nova.conf." msgstr "" #: ./doc/image-guide/section_windows-example.xml8(title) msgid "Example: Microsoft Windows image" msgstr "" #: ./doc/image-guide/section_windows-example.xml9(para) msgid "" "We do not yet have a fully documented example of how to create a Microsoft " "Windows image. You can use libvirt to install Windows from an installation " "DVD using the same approach as with the CentOS and Ubuntu examples. Once the" " initial install is done, you will need to perform some Windows-specific " "customizations." msgstr "" #: ./doc/image-guide/section_windows-example.xml14(title) msgid "Install VirtIO drivers" msgstr "" #: ./doc/image-guide/section_windows-example.xml15(para) msgid "" "Installing the VirtIO paravirtualizaion" " drivers for Windows will improve virtual machine performance when " "using KVM as the hypervisor to run Windows." msgstr "" #: ./doc/image-guide/section_windows-example.xml20(title) msgid "Sysprep" msgstr "" #: ./doc/image-guide/section_windows-example.xml21(para) msgid "" "Microsoft has a special tool called Sysprep that must be run inside " "of a Windows guest to prepare it for use as a virtual machine image. On " "Windows 2012 server, invoke sysprep, as follows: " msgstr "" #: ./doc/image-guide/section_windows-example.xml28(title) msgid "cloudbase-init" msgstr "" #: ./doc/image-guide/section_windows-example.xml29(para) msgid "" "cloudbase-init is a Windows port of cloud-init that should be " "installed inside of the guest. The source code is available on github." msgstr "" #: ./doc/image-guide/section_windows-example.xml35(title) msgid "Jordan Rinke's OpenStack Windows resources" msgstr "" #: ./doc/image-guide/section_windows-example.xml36(para) msgid "" "Jordan Rinke maintains a collection of " "resources for managing OpenStack Windows virtual machine guests." msgstr "" #: ./doc/image-guide/section_windows-example.xml41(title) msgid "Windows instances require the timezone to be \"localtime\"" msgstr "" #: ./doc/image-guide/section_windows-example.xml42(para) msgid "" "When uploading Windows images, you must set the os_type " "parameter to windows, which causes instances to use the " "local time zone. Failing to set this will cause the clock timezone to be " "UTC, which has unexpected side effects in Windows." msgstr "" #: ./doc/image-guide/section_freebsd-example.xml8(title) msgid "Example: FreeBSD image" msgstr "" #: ./doc/image-guide/section_freebsd-example.xml9(para) msgid "" "We do not yet have a fully documented example of how to create a FreeBSD " "image." msgstr "" #: ./doc/image-guide/section_freebsd-example.xml11(para) msgid "" "See the bsd-" "cloudinit project for information on how to build a FreeBSD VM image " "that works with OpenStack." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/image-guide/ch_creating_images_manually.xml82(None) msgid "" "@@image: 'figures/virt-manager-new.png'; " "md5=3528ebfc1b945b7dd80a34897b8fe98e" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml10(title) msgid "Create images manually" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml11(para) msgid "" "Creating a new image is a step done outside of your OpenStack installation. " "You create the new image manually on your own system and then upload the " "image to your cloud." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml15(para) msgid "" "To create a new image, you will need the installation CD or DVD ISO file for" " the guest operating system. You'll also need access to a virtualization " "tool. You can use KVM for this. Or, if you have a GUI desktop virtualization" " tool (such as, VMWare Fusion and VirtualBox), you can use that instead and " "just convert the file to raw once you're done." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml21(para) msgid "" "When you create a new virtual machine image, you will need to connect to the" " graphical console of the hypervisor, which acts as the virtual machine's " "display and allows you to interact with the guest operating system's " "installer using your keyboard and mouse. KVM can expose the graphical " "console using the VNC " "(Virtual Network Computing) protocol or the newer SPICE protocol. We'll use the VNC protocol here, since " "you're more likely to be able to find a VNC client that works on your local " "desktop." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml34(title) msgid "Verify the libvirt default network is running" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml35(para) msgid "" "Before starting a virtual machine with libvirt, verify that the libvirt " "\"default\" network has been started. This network must be active for your " "virtual machine to be able to connect out to the network. Starting this " "network will create a Linux bridge (usually called " "virbr0), iptables rules, and a dnsmasq process that will " "serve as a DHCP server." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml42(para) msgid "" "To verify that the libvirt \"default\" network is enabled, use the " " command and verify that the \"default\" network is active:" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml49(para) msgid "If the network is not active, start it by doing:" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml53(title) msgid "Use the virt-manager X11 GUI" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml54(para) msgid "" "If you plan to create a virtual machine image on a machine that can run X11 " "applications, the simplest way to do so is to use the GUI, " "which is installable as the virt-manager package on both " "Fedora-based and Debian-based systems. This GUI has an embedded VNC client " "in it that will let you view and interact with the guest's graphical " "console." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml62(para) msgid "" "If you are building the image on a headless server, and you have an X server" " on your local machine, you can launch  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 "" #: ./doc/image-guide/ch_creating_images_manually.xml73(para) 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 "" #: ./doc/image-guide/ch_creating_images_manually.xml70(para) msgid "" "If the account you use to ssh into your server does not have permissions to " "run libvirt, but has sudo privileges, do:" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml78(para) msgid "" "Click the \"New\" button at the top-left and step through the instructions. " "You will be shown a series of dialog boxes that will allow " "you to specify information about the virtual machine." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml87(para) msgid "" "When using qcow2 format images you should check the option 'customize before" " install', go to disk properties and explicitly select the qcow2 format. " "This ensures the virtual machine disk size will be correct." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml95(title) msgid "Use virt-install and connect by using a local VNC client" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml97(para) msgid "" "If you do not wish to use virt-manager (for example, you do not want to " "install the dependencies on your server, you don't have an X server running " "locally, the X11 forwarding over SSH isn't working), you can use the " " tool to boot the virtual machine through libvirt and " "connect to the graphical console from a VNC client installed on your local " "machine." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml105(para) 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), and Vinagre (GNOME)." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml120(para) msgid "" "The following example shows how to use the command to " "create an empty image file command to start up a virtual " "machine using that image file. As root:" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml154(para) 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 "" #: ./doc/image-guide/ch_creating_images_manually.xml137(para) 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's default network. There is a VNC server that is listening on all " "interfaces, and libvirt will not attempt to launch a VNC client " "automatically nor try to display the text console (--no-" "autoconsole). Finally, libvirt will attempt to optimize the " "configuration for a Linux guest running a RHEL 6.x " "distribution." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml163(para) msgid "" "Run the command to see a range of allowed --os-" "variant options." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml167(replaceable) msgid "vm-name" msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml166(para) msgid "Use the command to get the VNC port number." msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml171(para) 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 to a VNC client " "running on your local machine to display :1 on the remote machine and step " "through the installation process." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml6(title) msgid "Disk and container formats for images" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml8(para) msgid "" "When you add an image to the Image Service, you can specify its disk and " "container formats." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml11(title) msgid "Disk formats" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml12(para) msgid "" "The disk format of a virtual machine image is the format of the underlying " "disk image. Virtual appliance vendors have different formats for laying out " "the information contained in a virtual machine disk image." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml16(para) msgid "Set the disk format for your image to one of the following values:" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml20(para) msgid "" "raw. An unstructured disk image format; if you have a " "file without an extension it is possibly a raw format" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml25(para) msgid "" "vhd. The VHD disk format, a common disk format used by " "virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml31(para) msgid "" "vmdk. Common disk format supported by many common virtual" " machine monitors" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml36(para) msgid "" "vdi. Supported by VirtualBox virtual machine monitor and " "the QEMU emulator" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml41(para) msgid "" "iso. An archive format for the data contents of an " "optical disc, such as CD-ROM." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml46(para) msgid "" "qcow2. Supported by the QEMU emulator that can expand " "dynamically and supports Copy on Write" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml51(para) #: ./doc/image-guide/section_glance_image-formats.xml87(para) msgid "aki. An Amazon kernel image." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml55(para) #: ./doc/image-guide/section_glance_image-formats.xml91(para) msgid "ari. An Amazon ramdisk image." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml59(para) #: ./doc/image-guide/section_glance_image-formats.xml95(para) msgid "ami. An Amazon machine image." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml65(title) msgid "Container formats" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml66(para) msgid "" "The container format indicates whether the virtual machine image is in a " "file format that also contains metadata about the actual virtual machine." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml70(para) 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 "" #: ./doc/image-guide/section_glance_image-formats.xml75(para) msgid "" "You can set the container format for your image to one of the following " "values:" msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml79(para) msgid "" "bare. The image does not have a container or metadata " "envelope." msgstr "" #: ./doc/image-guide/section_glance_image-formats.xml83(para) msgid "ovf. The OVF container format." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml7(title) msgid "Image metadata" msgstr "Image metadata" #: ./doc/image-guide/section_glance-image-metadata.xml9(para) msgid "" "You can associate metadata with an image using the --property " "key=value " "argument to or . For example:" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml14(replaceable) msgid "img-uuid" msgstr "img-uuid" #: ./doc/image-guide/section_glance-image-metadata.xml15(para) msgid "" "If the following properties are set on an image, and the " "ImagePropertiesFilter scheduler filter is enabled (which it is by default), " "then the scheduler will only consider compute hosts that satisfy these " "properties:" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml20(term) msgid "architecture" msgstr "architecture" #: ./doc/image-guide/section_glance-image-metadata.xml31(literal) msgid "alpha" msgstr "alpha" #: ./doc/image-guide/section_glance-image-metadata.xml35(link) msgid "DEC 64-bit RISC" msgstr "DEC 64-bit RISC" #: ./doc/image-guide/section_glance-image-metadata.xml40(literal) msgid "armv7l" msgstr "armv7l" #: ./doc/image-guide/section_glance-image-metadata.xml44(link) msgid "ARM Cortex-A7 MPCore" msgstr "ARM Cortex-A7 MPCore" #: ./doc/image-guide/section_glance-image-metadata.xml49(literal) msgid "cris" msgstr "cris" #: ./doc/image-guide/section_glance-image-metadata.xml53(link) msgid "Ethernet, Token Ring, AXis - Code Reduced Instruction Set" msgstr "Ethernet, Token Ring, AXis - Code Reduced Instruction Set" #: ./doc/image-guide/section_glance-image-metadata.xml58(literal) msgid "i686" msgstr "i686" #: ./doc/image-guide/section_glance-image-metadata.xml60(para) msgid "" "Intel sixth-generation " "x86 (P6 micro architecture)" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml68(literal) msgid "ia64" msgstr "ia64" #: ./doc/image-guide/section_glance-image-metadata.xml72(link) msgid "Itanium" msgstr "Itanium" #: ./doc/image-guide/section_glance-image-metadata.xml77(literal) msgid "lm32" msgstr "lm32" #: ./doc/image-guide/section_glance-image-metadata.xml81(link) msgid "Lattice Micro32" msgstr "Lattice Micro32" #: ./doc/image-guide/section_glance-image-metadata.xml86(literal) msgid "m68k" msgstr "m68k" #: ./doc/image-guide/section_glance-image-metadata.xml90(link) msgid "Motorola 68000" msgstr "Motorola 68000" #: ./doc/image-guide/section_glance-image-metadata.xml95(literal) msgid "microblaze" msgstr "microblaze" #: ./doc/image-guide/section_glance-image-metadata.xml99(link) msgid "Xilinx 32-bit FPGA (Big Endian)" msgstr "Xilinx 32-bit FPGA (Big Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml104(literal) msgid "microblazeel" msgstr "microblazeel" #: ./doc/image-guide/section_glance-image-metadata.xml108(link) msgid "Xilinx 32-bit FPGA (Little Endian)" msgstr "Xilinx 32-bit FPGA (Little Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml113(literal) msgid "mips" msgstr "mips" #: ./doc/image-guide/section_glance-image-metadata.xml117(link) msgid "MIPS 32-bit RISC (Big Endian)" msgstr "MIPS 32-bit RISC (Big Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml122(literal) msgid "mipsel" msgstr "mipsel" #: ./doc/image-guide/section_glance-image-metadata.xml126(link) msgid "MIPS 32-bit RISC (Little Endian)" msgstr "MIPS 32-bit RISC (Little Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml131(literal) msgid "mips64" msgstr "mips64" #: ./doc/image-guide/section_glance-image-metadata.xml135(link) msgid "MIPS 64-bit RISC (Big Endian)" msgstr "MIPS 64-bit RISC (Big Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml140(literal) msgid "mips64el" msgstr "mips64el" #: ./doc/image-guide/section_glance-image-metadata.xml144(link) msgid "MIPS 64-bit RISC (Little Endian)" msgstr "MIPS 64-bit RISC (Little Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml149(literal) msgid "openrisc" msgstr "openrisc" #: ./doc/image-guide/section_glance-image-metadata.xml153(link) msgid "OpenCores RISC" msgstr "OpenCores RISC" #: ./doc/image-guide/section_glance-image-metadata.xml158(literal) msgid "parisc" msgstr "parisc" #: ./doc/image-guide/section_glance-image-metadata.xml162(link) msgid "HP Precision Architecture RISC" msgstr "HP Precision Architecture RISC" #: ./doc/image-guide/section_glance-image-metadata.xml167(literal) msgid "parisc64" msgstr "parisc64" #: ./doc/image-guide/section_glance-image-metadata.xml171(link) msgid "HP Precision Architecture 64-bit RISC" msgstr "HP Precision Architecture 64-bit RISC" #: ./doc/image-guide/section_glance-image-metadata.xml176(literal) msgid "ppc" msgstr "ppc" #: ./doc/image-guide/section_glance-image-metadata.xml180(link) msgid "PowerPC 32-bit" msgstr "PowerPC 32-bit" #: ./doc/image-guide/section_glance-image-metadata.xml185(literal) msgid "ppc64" msgstr "ppc64" #: ./doc/image-guide/section_glance-image-metadata.xml189(link) msgid "PowerPC 64-bit" msgstr "PowerPC 64-bit" #: ./doc/image-guide/section_glance-image-metadata.xml194(literal) msgid "ppcemb" msgstr "ppcemb" #: ./doc/image-guide/section_glance-image-metadata.xml198(link) msgid "PowerPC (Embedded 32-bit)" msgstr "PowerPC (Embedded 32-bit)" #: ./doc/image-guide/section_glance-image-metadata.xml203(literal) msgid "s390" msgstr "s390" #: ./doc/image-guide/section_glance-image-metadata.xml207(link) msgid "IBM Enterprise Systems Architecture/390" msgstr "IBM Enterprise Systems Architecture/390" #: ./doc/image-guide/section_glance-image-metadata.xml212(literal) msgid "s390x" msgstr "s390x" #: ./doc/image-guide/section_glance-image-metadata.xml216(link) msgid "S/390 64-bit" msgstr "S/390 64-bit" #: ./doc/image-guide/section_glance-image-metadata.xml221(literal) msgid "sh4" msgstr "sh4" #: ./doc/image-guide/section_glance-image-metadata.xml225(link) msgid "SuperH SH-4 (Little Endian)" msgstr "SuperH SH-4 (Little Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml230(literal) msgid "sh4eb" msgstr "sh4eb" #: ./doc/image-guide/section_glance-image-metadata.xml234(link) msgid "SuperH SH-4 (Big Endian)" msgstr "SuperH SH-4 (Big Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml239(literal) msgid "sparc" msgstr "sparc" #: ./doc/image-guide/section_glance-image-metadata.xml243(link) msgid "Scalable Processor Architecture, 32-bit" msgstr "Scalable Processor Architecture, 32-bit" #: ./doc/image-guide/section_glance-image-metadata.xml248(literal) msgid "sparc64" msgstr "sparc64" #: ./doc/image-guide/section_glance-image-metadata.xml252(link) msgid "Scalable Processor Architecture, 64-bit" msgstr "Scalable Processor Architecture, 64-bit" #: ./doc/image-guide/section_glance-image-metadata.xml257(literal) msgid "unicore32" msgstr "unicore32" #: ./doc/image-guide/section_glance-image-metadata.xml261(link) msgid "Microprocessor Research and Development Center RISC Unicore32" msgstr "Microprocessor Research and Development Center RISC Unicore32" #: ./doc/image-guide/section_glance-image-metadata.xml267(literal) msgid "x86_64" msgstr "x86_64" #: ./doc/image-guide/section_glance-image-metadata.xml271(link) msgid "64-bit extension of IA-32" msgstr "64-bit extension of IA-32" #: ./doc/image-guide/section_glance-image-metadata.xml276(literal) msgid "xtensa" msgstr "xtensa" #: ./doc/image-guide/section_glance-image-metadata.xml280(link) msgid "Tensilica Xtensa configurable microprocessor core" msgstr "Tensilica Xtensa configurable microprocessor core" #: ./doc/image-guide/section_glance-image-metadata.xml285(literal) msgid "xtensaeb" msgstr "xtensaeb" #: ./doc/image-guide/section_glance-image-metadata.xml289(link) msgid "Tensilica Xtensa configurable microprocessor core (Big Endian)" msgstr "Tensilica Xtensa configurable microprocessor core (Big Endian)" #: ./doc/image-guide/section_glance-image-metadata.xml22(para) msgid "" "The CPU architecture that must be supported by the hypervisor. For example, " "x86_64, arm, or " "ppc64. Run to get the architecture of a " "machine. We strongly recommend using the architecture data vocabulary " "defined by the libosinfo project " "for this purpose. Recognized values for this field are: " msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml299(term) msgid "hypervisor_type" msgstr "hypervisor_type" #: ./doc/image-guide/section_glance-image-metadata.xml301(para) msgid "" "The hypervisor type. Allowed values include: xen, " "qemu, kvm, lxc, " "uml, vmware, " "hyperv." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml308(term) msgid "vm_mode" msgstr "vm_mode" #: ./doc/image-guide/section_glance-image-metadata.xml314(literal) msgid "hvm" msgstr "hvm" #: ./doc/image-guide/section_glance-image-metadata.xml316(para) msgid "Fully virtualized. This is the mode used by QEMU and KVM." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml321(literal) msgid "xen" msgstr "xen" #: ./doc/image-guide/section_glance-image-metadata.xml323(para) msgid "Xen 3.0 paravirtualized." msgstr "Xen 3.0 paravirtualized." #: ./doc/image-guide/section_glance-image-metadata.xml327(literal) msgid "uml" msgstr "uml" #: ./doc/image-guide/section_glance-image-metadata.xml329(para) msgid "User Mode Linux paravirtualized." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml333(literal) msgid "exe" msgstr "exe" #: ./doc/image-guide/section_glance-image-metadata.xml335(para) msgid "Executables in containers. This is the mode used by LXC." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml310(para) msgid "" "The virtual machine mode. This represents the host/guest ABI (application " "binary interface) used for the virtual machine. Allowed values " "are:" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml342(para) msgid "The following metadata properties are specific to the XenAPI driver:" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml344(term) msgid "auto_disk_config" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml346(para) msgid "" "A boolean option. If true, the root partition on the disk will be " "automatically resized before the instance boots. This value is only taken " "into account by the Compute service when using a Xen-based hypervisor with " "the XenAPI driver. The Compute service will only attempt to resize if there " "is a single partition on the image, and only if the partition is in ext3 or " "ext4 format." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml355(term) msgid "os_type" msgstr "os_type" #: ./doc/image-guide/section_glance-image-metadata.xml357(para) msgid "" "The operating system installed on the image. For example, " "linux or windows. The XenAPI driver " "contains logic that will take different actions depending on the value of " "the os_type parameter of the image. For example, for images where " "os_type=windows, it creates a FAT32-based swap partition " "instead of a Linux swap partition, and it limits the injected host name to " "less than 16 characters." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml373(term) msgid "hw_video_model" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml375(para) msgid "" "The video image driver used. Allowed values include: vga," " cirrus, vmvga, xen" " and qxl." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml369(para) msgid "" "The following metadata properties are specific to the libvirt API driver: " "" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml384(para) msgid "" "The following metadata properties are specific to the VMware API driver:" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml387(term) msgid "vmware_adaptertype" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml389(para) msgid "" "Indicates the virtual SCSI or IDE controller used by the hypervisor. Allowed" " values: lsiLogic, busLogic, " "ide" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml395(term) msgid "vmware_ostype" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml397(para) msgid "" "A VMware GuestID which describes the operating system installed in the " "image. This will be passed to the hypervisor when creating a virtual " "machine. See thinkvirt.com for a " "list of valid values. If this is not specified, it will default to " "otherGuest." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml406(term) msgid "vmware_image_version" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml408(para) msgid "Currently unused, set it to 1." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml412(para) msgid "" "To assist end-users in utilizing images, you may wish to put additional " "common metadata on Glance images. By community agreement, the following " "metadata keys may be used across Glance installations for the purposes " "described, as follows." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml417(term) msgid "instance_uuid" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml419(para) msgid "" "For snapshot images, this is the UUID of the server used to create this " "image." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml425(term) msgid "kernel_id" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml427(para) msgid "" "The ID of image stored in Glance that should be used as the kernel when " "booting an AMI-style image." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml434(term) msgid "ramdisk_id" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml436(para) msgid "" "The ID of image stored in Glance that should be used as the ramdisk when " "booting an AMI-style image." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml443(term) msgid "os_version" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml445(para) msgid "The operating system version as specified by the distributor." msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml451(term) msgid "os_distro" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml464(literal) msgid "arch" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml466(para) msgid "This is: Arch Linux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml469(para) msgid "" "Do not use: archlinux, or " "org.archlinux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml477(literal) msgid "centos" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml479(para) msgid "This is: Community Enterprise Operating System" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml482(para) msgid "" "Do not use: org.centos, or CentOS" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml490(literal) msgid "debian" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml492(para) msgid "This is: Debian" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml495(para) msgid "" "Do not use: Debian, or org.debian" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml503(literal) msgid "fedora" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml505(para) msgid "This is: Fedora" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml508(para) msgid "" "Do not use: Fedora, org.fedora, or " "org.fedoraproject" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml517(literal) msgid "freebsd" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml519(para) msgid "This is: FreeBSD" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml522(para) msgid "" "Do not use: org.freebsd, freeBSD, or " "FreeBSD" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml531(literal) msgid "gentoo" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml533(para) msgid "This is: Gentoo Linux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml536(para) msgid "" "Do not use: Gentoo, or org.gentoo" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml544(literal) msgid "mandrake" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml546(para) msgid "This is: Mandrakelinux (MandrakeSoft)" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml549(para) msgid "" "Do not use: mandrakelinux, or " "MandrakeLinux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml557(literal) msgid "mandriva" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml559(para) msgid "This is: Mandriva Linux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml562(para) msgid "Do not use: mandrivalinux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml569(literal) msgid "mes" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml571(para) msgid "This is: Mandriva Enterprise Server" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml574(para) msgid "" "Do not use: mandrivaent, or mandrivaES" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml582(literal) msgid "msdos" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml584(para) msgid "This is: Microsoft Disc Operating System" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml587(para) msgid "Do not use: ms-dos" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml594(literal) msgid "netbsd" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml596(para) msgid "This is: NetBSD" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml599(para) msgid "" "Do not use: NetBSD, or org.netbsd" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml607(literal) msgid "netware" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml609(para) msgid "This is: Novell NetWare" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml612(para) msgid "Do not use: novell, or NetWare" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml620(literal) msgid "openbsd" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml622(para) msgid "This is: OpenBSD" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml625(para) msgid "" "Do not use: OpenBSD, or org.openbsd" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml633(literal) msgid "opensolaris" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml635(para) msgid "" "Do not use: OpenSolaris,or " "org.opensolaris" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml643(literal) msgid "opensuse" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml645(para) msgid "This is: openSUSE" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml648(para) msgid "" "Do not use: suse, SuSE, or " "org.opensuse" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml657(literal) msgid "rhel" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml659(para) msgid "This is: Red Hat Enterprise Linux" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml662(para) msgid "" "Do not use: redhat, RedHat, or " "com.redhat" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml671(literal) msgid "sled" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml673(para) msgid "This is: SUSE Linux Enterprise Desktop" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml676(para) msgid "Do not use: com.suse" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml683(literal) msgid "ubuntu" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml685(para) msgid "This is: Ubuntu" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml688(para) msgid "" "Do not use: Ubuntu, com.ubuntu, " "org.ubuntu, or canonical" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml698(literal) msgid "windows" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml700(para) msgid "This is: Microsoft Windows" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml703(para) msgid "" "Do not use: com.microsoft.server, or " "windoze" msgstr "" #: ./doc/image-guide/section_glance-image-metadata.xml453(para) msgid "" "The value of this property is the common name of the operating system " "distribution in all-lowercase. For this purpose, we use the same data " "vocabulary as the libosinfo " "project. Following are the recognized values for this property. In " "the interest of interoperability, please use only a recognized value for " "this field. The deprecated values are listed to assist you in searching for " "the recognized value. Allowed values are: " msgstr "" #: ./doc/image-guide/ch_converting.xml4(title) msgid "Converting between image formats" msgstr "" #: ./doc/image-guide/ch_converting.xml5(para) msgid "" "Converting images from one format to another is generally straightforward." msgstr "" #: ./doc/image-guide/ch_converting.xml7(title) msgid "qemu-img convert: raw, qcow2, VDI, VMDK" msgstr "" #: ./doc/image-guide/ch_converting.xml8(para) msgid "" "The command can do conversion between multiple formats, " "including raw, qcow2, VDI (VirtualBox), VMDK (VMWare) and VHD (Hyper-V)." msgstr "" #: ./doc/image-guide/ch_converting.xml12(caption) msgid "qemu-img format strings" msgstr "" #: ./doc/image-guide/ch_converting.xml16(th) msgid "Image format" msgstr "" #: ./doc/image-guide/ch_converting.xml17(th) msgid "Argument to qemu-img" msgstr "" #: ./doc/image-guide/ch_converting.xml22(td) #: ./doc/image-guide/ch_converting.xml23(literal) msgid "raw" msgstr "" #: ./doc/image-guide/ch_converting.xml30(td) msgid "VDI (VirtualBox)" msgstr "" #: ./doc/image-guide/ch_converting.xml31(literal) msgid "vdi" msgstr "" #: ./doc/image-guide/ch_converting.xml34(td) msgid "VMDK (VMWare)" msgstr "" #: ./doc/image-guide/ch_converting.xml35(literal) msgid "vmdk" msgstr "" #: ./doc/image-guide/ch_converting.xml38(td) msgid "VHD (Hyper-V)" msgstr "" #: ./doc/image-guide/ch_converting.xml39(literal) msgid "vpc" msgstr "" #: ./doc/image-guide/ch_converting.xml43(para) msgid "" "This example will convert a raw image file named centos63.dsk to a qcow2 " "image file." msgstr "" #: ./doc/image-guide/ch_converting.xml47(para) msgid "To convert from vmdk to raw, you would do: " msgstr "" #: ./doc/image-guide/ch_converting.xml51(para) msgid "" "The -f format flag is " "optional. If omitted, qemu-img will try to infer the image format." msgstr "" #: ./doc/image-guide/ch_converting.xml57(title) msgid "VBoxManage: VDI (VirtualBox) to raw" msgstr "" #: ./doc/image-guide/ch_converting.xml58(para) msgid "" "If you've created a VDI image using VirtualBox, you can convert it to raw " "format using the command-line tool that ships with " "VirtualBox. On Mac OS X, 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 "" #: ./doc/image-guide/ch_obtaining_images.xml6(title) msgid "Get images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml8(para) msgid "" "The simplest way to obtain a virtual machine image that works with OpenStack" " is to download one that someone else has already created." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml11(title) msgid "CirrOS (test) images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml12(para) msgid "" "CirrOS is a minimal Linux distribution that was designed for use as a test " "image on clouds such as OpenStack Compute. You can download a CirrOS image " "in various formats from the CirrOS Launchpad download " "page." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml21(para) msgid "" "In a CirrOS image, the login account is cirros. The " "password is cubswin:)" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml16(para) msgid "" "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " "format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.1-x86_64-disk.img" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml27(title) msgid "Official Ubuntu images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml28(para) msgid "" "Canonical maintains an official set of Ubuntu-based images." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml30(para) msgid "" "Images are arranged by Ubuntu release, and by image release date, with " "\"current\" being the most recent. For example, the page that contains the " "most recently built image for Ubuntu 12.04 \"Precise Pangolin\" is http://cloud-" "images.ubuntu.com/precise/current/. Scroll to the bottom of the page " "for links to images that can be downloaded directly." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml40(para) msgid "" "In an Ubuntu cloud image, the login account is ubuntu." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml36(para) msgid "" "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " "format. The most recent version of the 64-bit QCOW2 image for Ubuntu 12.04 " "is precise-server-cloudimg-" "amd64-disk1.img." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml45(title) msgid "Official Red Hat Enterprise Linux images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml46(para) msgid "" "Red Hat maintains an official Red Hat Enterprise Linux 6 cloud image. A " "valid Red Hat Enterprise Linux 6 subscription is required to download the " "KVM" " Guest Image." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml53(para) msgid "" "A boot.iso" " image is also available. This is the same as the " "boot.iso file provided on the Red Hat Enterprise Linux " "installation DVD. It is a minimal image suitable for kickstarting operating " "system installation over a network." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml63(title) msgid "Official Fedora images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml64(para) msgid "" "The Fedora project maintains a list of official cloud images at . The images include the " "cloud-init utility to support key" " and user data injection. The default user name is fedora." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml72(title) msgid "Official openSUSE and SLES images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml73(para) msgid "" "SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images" " for direct download. Instead, they provide a web-based tool called SUSE Studio that you can use to build " "openSUSE and SLES images." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml79(para) msgid "" "For example, Christian Berendt used openSUSE to create a test openSUSE 12.3 image." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml84(title) msgid "Official images from other Linux distributions" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml85(para) msgid "" "As of this writing, we are not aware of other distributions that provide " "images for download." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml88(title) msgid "Rackspace Cloud Builders (multiple distros) images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml90(para) msgid "" "Rackspace Cloud Builders maintains a list of pre-built images from various " "distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can " "be found at rackerjoe/oz-image-build on Github." msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml96(title) msgid "Microsoft Windows images" msgstr "" #: ./doc/image-guide/ch_obtaining_images.xml97(para) msgid "" "Cloudbase Solutions hosts an OpenStack Windows Server 2012 " "Standard Evaluation image that runs on Hyper-V, KVM, and " "XenServer/XCP." msgstr "" #. Put one translator per line, in the form of NAME , YEAR1, YEAR2 #: ./doc/image-guide/ch_obtaining_images.xml0(None) msgid "translator-credits" msgstr "Olivier Buisson , 2012 | Cloudwatt Team , 2013"