diff --git a/RELEASENOTES.rst b/RELEASENOTES.rst index 722151cb25..7a8e3b4442 100644 --- a/RELEASENOTES.rst +++ b/RELEASENOTES.rst @@ -30,6 +30,11 @@ Operations Guide * Shared File Systems chapter added. +Virtual Machine Image Guide +--------------------------- + +* RST conversion finished. + Translations ------------ diff --git a/doc-tools-check-languages.conf b/doc-tools-check-languages.conf index f07c95b3e8..10bf921b20 100644 --- a/doc-tools-check-languages.conf +++ b/doc-tools-check-languages.conf @@ -1,20 +1,15 @@ # directories to be set up declare -A DIRECTORIES=( - ["fr"]="common glossary image-guide" - ["ja"]="common glossary image-guide" - ["zh_CN"]="common glossary arch-design image-guide" + ["zh_CN"]="common glossary arch-design" ) # books to be built declare -A BOOKS=( - ["fr"]="image-guide" - ["ja"]="image-guide user-guide user-guide-admin install-guide networking-guide" - ["zh_CN"]="arch-design image-guide" + ["ja"]="user-guide user-guide-admin install-guide networking-guide" ) # draft books declare -A DRAFTS=( - ["fr"]="image-guide" ["ja"]="install-guide networking-guide" ) @@ -30,6 +25,7 @@ DOC_DIR="doc/" # project-config/jenkins/scripts/common_translation_update.sh declare -A SPECIAL_BOOKS=( ["admin-guide-cloud"]="RST" + ["image-guide"]="RST" ["install-guide"]="RST" ["networking-guide"]="RST" ["user-guide"]="RST" @@ -38,7 +34,6 @@ declare -A SPECIAL_BOOKS=( ["contributor-guide"]="skip" ["arch-design-rst"]="skip" ["config-ref-rst"]="skip" - ["image-guide-rst"]="skip" # This needs special handling, handle it with the RST tools. ["common-rst"]="RST" ) diff --git a/doc/image-guide/bk-imageguide.xml b/doc/image-guide/bk-imageguide.xml deleted file mode 100644 index 4bdbf0970a..0000000000 --- a/doc/image-guide/bk-imageguide.xml +++ /dev/null @@ -1,52 +0,0 @@ - - - - OpenStack Virtual Machine Image Guide - -VM Image Guide - - - - - - - - OpenStack Foundation - - - - 2013 - 2014 - 2015 - OpenStack Foundation - - current - OpenStack - - - - Remaining licensing details are filled in by - the template. - - - - This guide describes how to obtain, create, and - modify virtual machine images that are compatible with - OpenStack. - - - - - - - - - - - - - diff --git a/doc/image-guide/ch_converting.xml b/doc/image-guide/ch_converting.xml deleted file mode 100644 index 58a0da1892..0000000000 --- a/doc/image-guide/ch_converting.xml +++ /dev/null @@ -1,82 +0,0 @@ - - - Converting between image formats - Converting images from one format to another is generally straightforward. - - qemu-img convert: raw, qcow2, qed, vdi, vmdk, vhd - The qemu-img convert command can do conversion between multiple - formats, including qcow2, qed, raw, vdi, vhd, and vmdk. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
qemu-img format strings
Image formatArgument to qemu-img
QCOW2 (KVM, Xen)qcow2
QED (KVM)qed
rawraw
VDI (VirtualBox)vdi
VHD (Hyper-V)vpc
VMDK (VMware)vmdk
- This example will convert a raw image file named centos7.img to a qcow2 image file. - - $ qemu-img convert -f raw -O qcow2 centos7.img centos7.qcow2 - - Run the following command to convert a vmdk image file to a raw image file. - $ qemu-img convert -f vmdk -O raw centos7.vmdk centos7.img - - Run the following command to convert a vmdk image file to a qcow2 image file. - $ qemu-img convert -f vmdk -O qcow2 centos7.vmdk centos7.qcow2 - - - - The -f format flag is optional. - If omitted, qemu-img will try to infer the image format. - When converting an image file with Windows OS, ensure the virtio driver is - installed. Otherwise, you will get a blue screen of death or BSOD when - launching the image due to lack of the virtio driver. Another option is to - set the image properties as below when you update the image in glance to - avoid this issue, but it will reduce performance significantly. - $ glance image-update --property hw_disk_bus='ide' image_id - - - - - VBoxManage: VDI (VirtualBox) to raw - If you've created a VDI image using VirtualBox, you can convert it to raw format using - the VBoxManage command-line tool that ships with VirtualBox. On Mac - OS X, and Linux, VirtualBox stores images by default in the ~/VirtualBox VMs/ - directory. The following example creates a raw image in the current directory from a - VirtualBox VDI image. - $ VBoxManage clonehd ~/VirtualBox\ VMs/fedora21.vdi fedora21.img --format raw - - diff --git a/doc/image-guide/ch_creating_images_automatically.xml b/doc/image-guide/ch_creating_images_automatically.xml deleted file mode 100644 index b50511e851..0000000000 --- a/doc/image-guide/ch_creating_images_automatically.xml +++ /dev/null @@ -1,184 +0,0 @@ - - - Tool support for image creation - - There are several tools that are designed to automate image - creation. -
- Diskimage-builder - Diskimage-builder is an automated disk image creation - tool that supports a variety of distributions and architectures. - Diskimage-builder (DIB) can build images for Fedora, - Red Hat Enterprise Linux, Ubuntu, Debian, CentOS, and openSUSE. - DIB is organized in a series of elements that build on top of - each other to create specific images. - To build an image, call the following script: -# disk-image-create ubuntu vm - This example creates a generic, bootable Ubuntu image of the latest - release. - Further customization could be accomplished by setting - environment variables or adding elements to the command-line: -# disk-image-create -a armhf ubuntu vm - This example creates the image as before, but for arm architecture. - More elements are available in the - git source directory and documented in the diskimage-builder elements documentation. - -
- -
- Oz - 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: -# yum install oz - - As of this writing, there are no Oz packages for Ubuntu, - so you will need to either install from the source or build your - own .deb file. - - 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. - 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. -<template> - <name>centos64</name> - <os> - <name>CentOS-6</name> - <version>4</version> - <arch>x86_64</arch> - <install type='iso'> - <iso>http://mirror.rackspace.com/CentOS/6/isos/x86_64/CentOS-6.4-x86_64-bin-DVD1.iso</iso> - </install> - <rootpw>CHANGE THIS TO YOUR ROOT PASSWORD</rootpw> - </os> - <description>CentOS 6.4 x86_64</description> - <repositories> - <repository name='epel-6'> - <url>http://download.fedoraproject.org/pub/epel/6/$basearch</url> - <signed>no</signed> - </repository> - </repositories> - <packages> - <package name='epel-release'/> - <package name='cloud-utils'/> - <package name='cloud-init'/> - </packages> - <commands> - <command name='update'> -yum -y update -yum clean all -sed -i '/^HWADDR/d' /etc/sysconfig/network-scripts/ifcfg-eth0 -echo -n > /etc/udev/rules.d/70-persistent-net.rules -echo -n > /lib/udev/rules.d/75-persistent-net-generator.rules - </command> - </commands> -</template> - - 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. - After Oz completes the initial OS install using the kickstart file, - it customizes the image with an update. It also removes any reference to the eth0 - device that libvirt creates while Oz does the customizing, as - specified in the command section of the XML - file. - To run this: - # oz-install -d3 -u centos64.tdl -x centos64-libvirt.xml - - - The -d3 flag tells Oz to show - status information as it runs. - - - The -u tells Oz to do the - customization (install extra packages, run the commands) - once it does the initial install. - - - 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). - - - If you leave out the -u flag, or - you want to edit the file to do additional customizations, you can - use the oz-customize command, using the libvirt - XML file that oz-install creates. For example: - # oz-customize -d3 centos64.tdl centos64-libvirt.xml - Oz will invoke libvirt to boot the image inside of KVM, then Oz will - ssh into the instance and perform the customizations. -
-
- VMBuilder - 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. - The Ubuntu Server Guide - has documentation on how to use VMBuilder to create an - Ubuntu image. -
-
- VeeWee - - VeeWee is often used to build Vagrant - boxes, but it can also be used to build KVM images. -
-
- Packer - - Packer is a tool for creating machine images for multiple platforms - from a single source configuration. - -
-
- imagefactory - 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. -
-
- SUSE Studio - 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. -
- diff --git a/doc/image-guide/ch_creating_images_manually.xml b/doc/image-guide/ch_creating_images_manually.xml deleted file mode 100644 index 2c9b0ef011..0000000000 --- a/doc/image-guide/ch_creating_images_manually.xml +++ /dev/null @@ -1,185 +0,0 @@ - - -%openstack; -]> - - Create images manually - 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. - 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 or VirtualBox), you can use that instead and just - convert the file to raw once you are done. - 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. -
- Verify the libvirt default network is running - 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. - To verify that the libvirt "default" network is enabled, - use the virsh net-list command and - verify that the "default" network is active: - # virsh net-list -Name State Autostart ------------------------------------------ -default active yes - If the network is not active, start it by doing: - # virsh net-start default -
-
- Use the virt-manager X11 GUI - 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 virt-manager GUI, - which is installable as the - virt-manager package on both - Fedora-based and Debian-based systems. This GUI has an - embedded VNC client that will let you view and - interact with the guest's graphical console. - If you are building the image on a headless server, and - you have an X server on your local machine, you can launch - virt-manager using ssh X11 - forwarding to access the GUI. Since virt-manager interacts - directly with libvirt, you typically need to be root to - access it. If you can ssh directly in as root (or with a - user that has permissions to interact with libvirt), - do:$ ssh -X root@server virt-manager - If the account you use to ssh into your server does not - have permissions to run libvirt, but has sudo privileges, do:$ ssh -X root@server -$ sudo virt-manager - The -X flag passed to ssh - will enable X11 forwarding over ssh. If this does - not work, try replacing it with the - -Y flag. - - 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. - - 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. - -
-
- Use virt-install and connect by using a local VNC - client - 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 - virt-install tool to boot the - virtual machine through libvirt and connect to the - graphical console from a VNC client installed on your - local machine. - 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). - The following example shows how to use the - qemu-img command to create an empty - image file, and virt-install command to - start up a virtual machine using that image file. As - root: - # qemu-img create -f qcow2 /data/centos-6.4.qcow2 10G -# virt-install --virt-type kvm --name centos-6.4 --ram 1024 \ ---cdrom=/data/CentOS-6.4-x86_64-netinstall.iso \ ---disk path=/data/centos-6.4.qcow2,size=10,format=qcow2 \ ---network network=default \ ---graphics vnc,listen=0.0.0.0 --noautoconsole \ ---os-type=linux --os-variant=rhel6 - -Starting install... -Creating domain... | 0 B 00:00 -Domain installation still in progress. You can reconnect to -the console to complete the installation process. - - 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. - 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. - - Run the virt-install --os-variant - list command to see a range of allowed - --os-variant options. - Use the virsh vncdisplay - vm-name - command to get the VNC port number. - # virsh vncdisplay centos-6.4 -:1 - In the example above, the guest - centos-6.4 uses VNC display - :1, which corresponds to TCP port - 5901. You should be able to connect - a VNC client running on your local machine to display - :1 on the remote machine and step through the installation - process. -
- - - - - - diff --git a/doc/image-guide/ch_introduction.xml b/doc/image-guide/ch_introduction.xml deleted file mode 100644 index 30b176fdb7..0000000000 --- a/doc/image-guide/ch_introduction.xml +++ /dev/null @@ -1,140 +0,0 @@ - - - Introduction - 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. - To keep things brief, we'll sometimes use the term "image" instead of "virtual machine - image". - What is a virtual machine image? - A virtual machine image is a single file which contains a virtual disk that has a - bootable operating system installed on it. - Virtual machine images come in different formats, some of which are described below. - - - Raw - 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 - dd command. - We don't recommend creating raw images by dd'ing - block device files, we discuss how to create raw - images later. - - - - qcow2 - 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: - - Using sparse representation, so the image size is smaller. - - - Support for snapshots. - - - Because qcow2 is sparse, qcow2 images are typically smaller than raw images. Smaller images mean faster uploads, so it's often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. - - - Because raw images don't support snapshots, OpenStack Compute will - automatically convert raw image files to qcow2 as needed. - - - - - AMI/AKI/ARI - The AMI/AKI/ARI format was the initial image - format supported by Amazon EC2. The image consists of - three files: - AMI (Amazon Machine Image): - This is a virtual machine image in raw - format, as described above. - - - AKI (Amazon Kernel Image) - A kernel file that the hypervisor will - load initially to boot the image. For a - Linux machine, this would be a - vmlinuz file. - - - - ARI (Amazon Ramdisk Image) - An optional ramdisk file mounted at boot - time. For a Linux machine, this would be - an initrd - file. - - - - - UEC tarball - A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains an AMI - file, AKI file, and ARI file. - Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu cloud - solution that has been replaced by the OpenStack-based Ubuntu Cloud - Infrastructure. - - - - VMDK - VMware's ESXi hypervisor uses the VMDK (Virtual Machine Disk) format for images. - - - VDI - 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. - - - VHD - Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images. - - - VHDX - 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. - - - OVF - 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. - 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. - 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. - - - ISO - 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. - - - - diff --git a/doc/image-guide/ch_modifying_images.xml b/doc/image-guide/ch_modifying_images.xml deleted file mode 100644 index a7b2749b98..0000000000 --- a/doc/image-guide/ch_modifying_images.xml +++ /dev/null @@ -1,394 +0,0 @@ - - -%openstack; -]> - - Modify images - - 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. - 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. - -
- guestfish - The guestfish program is a tool from - the libguestfs project that allows you to modify - the files inside of a virtual machine image. - - guestfish does not mount the - image directly into the local file system. Instead, it - provides you with a shell interface that enables you - to view, edit, and delete files. Many of - guestfish commands, such as - touch, - chmod, and rm, - resemble traditional bash commands. - - - Example guestfish session - 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. - Assume that you have a CentOS qcow2 image called - centos63_desktop.img. Mount - the image in read-write mode as root, as - follows: - # guestfish --rw -a centos63_desktop.img - -Welcome to guestfish, the libguestfs filesystem interactive shell for -editing virtual machine filesystems. - -Type: 'help' for help on commands - 'man' to read the manual - 'quit' to quit the shell - -><fs> - This starts a guestfish session. Note that the - guestfish prompt looks like a fish: > - <fs>. - We must first use the run command - at the guestfish prompt before we can do anything - else. This will launch a virtual machine, which will - be used to perform all of the file - manipulations.><fs> run - We can now view the file systems in the image using the - list-filesystems - command:><fs> list-filesystems -/dev/vda1: ext4 -/dev/vg_centosbase/lv_root: ext4 -/dev/vg_centosbase/lv_swap: swapWe - need to mount the logical volume that contains the - root partition: - ><fs> mount /dev/vg_centosbase/lv_root / - Next, we want to delete a file. We can use the - rm guestfish command, which - works the same way it does in a traditional - shell. - ><fs> rm /etc/udev/rules.d/70-persistent-net.rulesWe - want to edit the ifcfg-eth0 file - to remove the HWADDR line. The - edit command will copy the file - to the host, invoke your editor, and then copy the - file back. - ><fs> edit /etc/sysconfig/network-scripts/ifcfg-eth0 - 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 touch - guestfish command to create an empty file, the - edit command to edit it, and - the chmod command to make it - executable.><fs> touch /etc/sysconfig/modules/8021q.modules -><fs> edit /etc/sysconfig/modules/8021q.modules - We add the following line to the file and save - it:modprobe 8021qThen - we set to executable: - ><fs> chmod 0755 /etc/sysconfig/modules/8021q.modules - We're done, so we can exit using the - exit - command:><fs> exit - - - Go further with guestfish - 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. - -
-
- guestmount - For some types of changes, you may find it easier to - mount the image's file system directly in the guest. The - guestmount program, also from the - libguestfs project, allows you to do so. - For example, to mount the root partition from our - centos63_desktop.qcow2 image to - /mnt, we can do: - - # guestmount -a centos63_desktop.qcow2 -m /dev/vg_centosbase/lv_root --rw /mnt - - 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:# guestmount -a centos63_desktop.qcow2 -i --rw /mntOnce - mounted, we could do things like list the installed - packages using - rpm:# rpm -qa --dbpath /mnt/var/lib/rpm - Once done, we - unmount:# umount /mnt -
-
- virt-* tools - The libguestfs project has a number of other - useful tools, including: - - virt-edit for editing a file - inside of an image. - - - virt-df for displaying free space - inside of an image. - - - virt-resize for resizing an - image. - - - virt-sysprep for preparing an - image for distribution (for example, delete - SSH host keys, remove MAC address info, or - remove user accounts). - - - virt-sparsify for making an image - sparse. - - - virt-p2v for converting a physical - machine to an image that runs on KVM. - - - virt-v2v for converting Xen and - VMware images to KVM images. - - - - Modify a single file inside of an image - This example shows how to use - virt-edit to modify a file. The - command can take either a filename as an argument with - the -a flag, or a domain name as an - argument with the -d flag. The - following examples shows how to use this to modify the - /etc/shadow file in instance - with libvirt domain name - instance-000000e1 that is - currently running: - - # virsh shutdown instance-000000e1 -# virt-edit -d instance-000000e1 /etc/shadow -# virsh start instance-000000e1 - - - - Resize an image - Here is an example of how to use - virt-resize to resize an image. - Assume we have a 16 GB Windows image in qcow2 format - that we want to resize to 50 GB. First, we use - virt-filesystems to identify - the - partitions:# virt-filesystems --long --parts --blkdevs -h -a /data/images/win2012.qcow2 -Name Type MBR Size Parent -/dev/sda1 partition 07 350M /dev/sda -/dev/sda2 partition 07 16G /dev/sda -/dev/sda device - 16G - - - In this case, it's the - /dev/sda2 partition that we - want to resize. We create a new qcow2 image and use - the virt-resize command to write a - resized copy of the original into the new - image: - # qemu-img create -f qcow2 /data/images/win2012-50gb.qcow2 50G -# virt-resize --expand /dev/sda2 /data/images/win2012.qcow2 \ - /data/images/win2012-50gb.qcow2 -Examining /data/images/win2012.qcow2 ... -********** - -Summary of changes: - -/dev/sda1: This partition will be left alone. - -/dev/sda2: This partition will be resized from 15.7G to 49.7G. The - filesystem ntfs on /dev/sda2 will be expanded using the - 'ntfsresize' method. - -********** -Setting up initial partition table on /data/images/win2012-50gb.qcow2 ... -Copying /dev/sda1 ... - 100% ⟦▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓⟧ 00:00 -Copying /dev/sda2 ... - 100% ⟦▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓⟧ 00:00 -Expanding /dev/sda2 using the 'ntfsresize' method ... - -Resize operation completed with no errors. Before deleting the old -disk, carefully check that the resized disk boots and works correctly. - - -
-
- Loop devices, kpartx, network block devices - 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. - 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. - - - Mount a raw image (without LVM) - If you have a raw virtual machine image that is not - using LVM to manage its partitions, use the - losetup command to find an - unused loop device. - # losetup -f -/dev/loop0 - In this example, /dev/loop0 is - free. Associate a loop device with the raw - image:# losetup /dev/loop0 fedora17.img - If the image only has a single partition, you can - mount the loop device - directly:# mount /dev/loop0 /mnt - If the image has multiple partitions, use - kpartx to expose the partitions - as separate devices (for example, - /dev/mapper/loop0p1), then - mount the partition that corresponds to the root file - system:# kpartx -av /dev/loop0 - If the image has, say three partitions (/boot, /, - swap), there should be one new device created per - partition:$ ls -l /dev/mapper/loop0p* -brw-rw---- 1 root disk 43, 49 2012-03-05 15:32 /dev/mapper/loop0p1 -brw-rw---- 1 root disk 43, 50 2012-03-05 15:32 /dev/mapper/loop0p2 -brw-rw---- 1 root disk 43, 51 2012-03-05 15:32 /dev/mapper/loop0p3To - mount the second partition, as - root:# mkdir /mnt/image -# mount /dev/mapper/loop0p2 /mntOnce - you're done, to clean - up:# umount /mnt -# kpartx -d /dev/loop0 -# losetup -d /dev/loop0 - - - Mount a raw image (with LVM) - If your partitions are managed with LVM, use losetup - and kpartx as in the previous example to expose the - partitions to the host. - # losetup -f -/dev/loop0 -# losetup /dev/loop0 rhel62.img -# kpartx -av /dev/loop0 - Next, you need to use the vgscan - command to identify the LVM volume groups and then - vgchange to expose the volumes - as devices: - # vgscan -Reading all physical volumes. This may take a while... - Found volume group "vg_rhel62x8664" using metadata type lvm2 -# vgchange -ay - 2 logical volume(s) in volume group "vg_rhel62x8664" now active -# mount /dev/vg_rhel62x8664/lv_root /mnt - Clean up when you're done: - # umount /mnt -# vgchange -an vg_rhel62x8664 -# kpartx -d /dev/loop0 -# losetup -d /dev/loop0 - - - Mount a qcow2 image (without LVM) - 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:# modprobe nbd max_part=16 - Assuming the first block device - (/dev/nbd0) is not currently - in use, we can expose the disk partitions using the - qemu-nbd and - partprobe commands. As - root:# qemu-nbd -c /dev/nbd0 image.qcow2 -# partprobe /dev/nbd0 - If the image has, say three partitions (/boot, /, - swap), there should be one new device created for - each partition: - $ ls -l /dev/nbd3* -brw-rw---- 1 root disk 43, 48 2012-03-05 15:32 /dev/nbd0 -brw-rw---- 1 root disk 43, 49 2012-03-05 15:32 /dev/nbd0p1 -brw-rw---- 1 root disk 43, 50 2012-03-05 15:32 /dev/nbd0p2 -brw-rw---- 1 root disk 43, 51 2012-03-05 15:32 /dev/nbd0p3 - - If the network block device you selected was - already in use, the initial - qemu-nbd command will fail - silently, and the - /dev/nbd3p{1,2,3} device - files will not be created. - - If the image partitions are not managed with LVM, - they can be mounted directly: - # mkdir /mnt/image -# mount /dev/nbd3p2 /mnt - When you're done, clean up: - # umount /mnt -# qemu-nbd -d /dev/nbd0 - - - Mount a qcow2 image (with LVM) - If the image partitions are managed with LVM, after - you use qemu-nbd and - partprobe, you must use - vgscan and vgchange - -ay in order to expose the LVM - partitions as devices that can be - mounted:# modprobe nbd max_part=16 -# qemu-nbd -c /dev/nbd0 image.qcow2 -# partprobe /dev/nbd0# vgscan - Reading all physical volumes. This may take a while... - Found volume group "vg_rhel62x8664" using metadata type lvm2 -# vgchange -ay - 2 logical volume(s) in volume group "vg_rhel62x8664" now active -# mount /dev/vg_rhel62x8664/lv_root /mnt - When you're done, clean - up:# umount /mnt -# vgchange -an vg_rhel62x8664 -# qemu-nbd -d /dev/nbd0 - -
- diff --git a/doc/image-guide/ch_obtaining_images.xml b/doc/image-guide/ch_obtaining_images.xml deleted file mode 100644 index 2e7e6dc08a..0000000000 --- a/doc/image-guide/ch_obtaining_images.xml +++ /dev/null @@ -1,178 +0,0 @@ - - - Get images - - The simplest way to obtain a virtual machine image that works with - OpenStack is to download one that someone else has already created. - Most of the images contain the - cloud-init package to - support SSH key pair and user data injection. Because many of the - images disable SSH password authentication by default, boot the - image with an injected key pair. You can SSH into the instance with - the private key and default login account. See the - OpenStack End User Guide for more information on how to - create and inject key pairs with OpenStack. -
- CentOS images - The CentOS project maintains official images for direct - download. - - - - CentOS 6 images - - - - - CentOS 7 images - - - - - In a CentOS cloud image, the login account is - centos. - -
-
- CirrOS (test) images - CirrOS is a minimal Linux distribution that was designed for use as a test image on - clouds such as OpenStack Compute. You can download a CirrOS image in various formats - from the CirrOS - download page. - If your deployment uses QEMU or KVM, we recommend using the images in qcow2 - format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.4-x86_64-disk.img. - - In a CirrOS image, the login account is cirros. The - password is cubswin:) - -
- -
- Official Ubuntu images - Canonical maintains an official - set of Ubuntu-based images. - Images are arranged by Ubuntu release, and by image release date, with "current" being - the most recent. For example, the page that contains the most recently built image for - Ubuntu 14.04 "Trusty Tahr" is http://cloud-images.ubuntu.com/trusty/current/. Scroll to the bottom of the - page for links to images that can be downloaded directly. - If your deployment uses QEMU or KVM, we recommend using the images in qcow2 - format. The most recent version of the 64-bit QCOW2 image for Ubuntu 14.04 is trusty-server-cloudimg-amd64-disk1.img. - In an Ubuntu cloud image, the login account is - ubuntu. - -
-
- Official Red Hat Enterprise Linux images - - Red Hat maintains official Red Hat Enterprise Linux cloud - images. A valid Red Hat Enterprise Linux subscription is required - to download these images. - - - - - Red Hat Enterprise Linux 7 KVM Guest Image - - - - - Red Hat Enterprise Linux 6 KVM Guest Image - - - - - - In a RHEL cloud image, the login account is - cloud-user. - - -
-
- Official Fedora images - The Fedora project maintains a list of official cloud images at - . - - In a Fedora cloud image, the login account is - fedora. - -
-
- Official openSUSE and SLES images - SUSE provides images for openSUSE. - For SUSE Linux Enterprise Server (SLES), custom images can be built with - a web-based tool called SUSE Studio. - SUSE Studio can also be used to build custom openSUSE images. -
-
- Official Debian images - Since January 2015, - Debian - provides images for direct download. They are now made at the - same time as the CD and DVD images of Debian. However, until Debian 8.0 - (aka Jessie) is out, these images are the weekly built images of the - testing distribution. - If you wish to build your own images of Debian 7.0 (aka Wheezy, the - current stable release of Debian), you can use the package which is - used to build the official Debian images. It is named - openstack-debian-images, and it - provides a simple script for building them. This package is available - in Debian Unstable, Debian Jessie, and through the wheezy-backports - repositories. To produce a Wheezy image, simply run: - # build-openstack-debian-image -r wheezy - If building the image for Wheezy, packages like - cloud-init, cloud-utils or - cloud-initramfs-growroot will be pulled from - wheezy-backports. Also, the current version of - bootlogd in Wheezy doesn't support logging to - multiple consoles, which is needed so that both the OpenStack - Dashboard console and the nova console-log - console works. However, a - fixed version is available from the non-official GPLHost - repository. To install it on top of the image, it is possible - to use the option of the - build-openstack-debian-image script, with this - kind of script as parameter: -#!/bin/sh - -cp bootlogd_2.88dsf-41+deb7u2_amd64.deb ${BODI_CHROOT_PATH} -chroot ${BODI_CHROOT_PATH} dpkg -i bootlogd_2.88dsf-41+deb7u2_amd64.deb -rm ${BODI_CHROOT_PATH}/bootlogd_2.88dsf-41+deb7u2_amd64.deb - - In a Debian image, the login account is admin. - -
-
- Official images from other Linux distributions - As of this writing, we are not aware of other distributions that provide images for download. -
-
- Rackspace Cloud Builders (multiple distros) - images - 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. -
-
- Microsoft Windows images - Cloudbase Solutions hosts an OpenStack Windows Server 2012 Standard Evaluation image that runs on - Hyper-V, KVM, and XenServer/XCP. -
- diff --git a/doc/image-guide/ch_openstack_images.xml b/doc/image-guide/ch_openstack_images.xml deleted file mode 100644 index 6f6dc31d13..0000000000 --- a/doc/image-guide/ch_openstack_images.xml +++ /dev/null @@ -1,549 +0,0 @@ - - -%openstack; -]> - - OpenStack Linux image requirements - - For a Linux-based image to have full functionality in an - OpenStack Compute cloud, there are a few requirements. For - some of these, you can fulfill the requirements by installing - the cloud-init package. Read - this section before you create your own image to be sure that - the image supports the OpenStack features that you plan to use. - - - Disk partitions and resize root partition on boot - (cloud-init) - - - No hard-coded MAC address information - - - SSH server running - - - Disable firewall - - - Access instance using ssh public key - (cloud-init) - - - Process user data and other metadata - (cloud-init) - - - Paravirtualized Xen support in Linux kernel (Xen - hypervisor only with Linux kernel version < - 3.0) - - -
- Disk partitions and resize root partition on boot - (cloud-init) - 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. - 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. - 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. - - Xen: 1 ext3/ext4 partition (no LVM, no /boot, no - swap) - 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: - - - auto_disk_config=True is - set as a property on the image in the image - registry. - - - The disk on the image has only one - partition. - - - The file system on the one partition is ext3 - or ext4. - - - 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. - - - Non-Xen with cloud-init/cloud-tools: One ext3/ext4 - partition (no LVM, no /boot, no swap) - You must configure these items for your - image: - - - The partition table for the image describes - the original size of the image. - - - The file system for the image fills the - original size of the image. - - - Then, during the boot process, you must: - - - Modify the partition table to make it aware - of the additional space: - - - If you do not use LVM, you must - modify the table to extend the - existing root partition to encompass - this additional space. - - - 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. - - - - - Resize the root volume file system. - - - The simplest way to support this is to - install in your image the: - - - cloud-utils - package, which contains the growpart - tool for extending partitions. - - - cloud-initramfs-growroot - package for Ubuntu, Debian and Fedora, which supports - resizing root partition on the first boot. - - - cloud-initramfs-growroot - package for Centos and RHEL. - - - cloud-init - package. - - - With these packages installed, the image - performs the root partition resize on boot. For - example, in the /etc/rc.local - file. These packages are in the Ubuntu and Debian - package repository, as well as the EPEL repository - (for Fedora/RHEL/CentOS/Scientific Linux - guests). - If you cannot install - cloud-initramfs-tools, Robert - Plestenjak has a GitHub project called linux-rootfs-resize that contains scripts - that update a ramdisk by using - growpart so that the image - resizes properly on boot. - 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). - - - Non-Xen without - <package>cloud-init</package>/<package>cloud-tools</package>: - LVM - 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. - Your script must do something like the following: - - Detect if any additional space is - available on the disk. For example, parse - the output of parted /dev/sda - --script "print - free". - - - Create a new LVM partition with the - additional space. For example, - parted /dev/sda --script - "mkpart lvm ...". - - - Create a new physical volume. For - example, pvcreate - /dev/sda6. - - - Extend the volume group with this - physical partition. For example, - vgextend - vg00 - /dev/sda6. - - - Extend the logical volume contained the - root partition by the amount of space. For - example, lvextend - /dev/mapper/node-root - /dev/sda6. - - - Resize the root file system. For - example, resize2fs - /dev/mapper/node-root. - - - You do not need a /boot - partition unless your image is an older Linux - distribution that requires that - /boot is not managed by - LVM. - -
-
- No hard-coded MAC address information - You must remove the network persistence rules in the - image because they cause the network interface in the - instance to come up as an interface other than eth0. This - is because your image has a record of the MAC address of - the network interface card when it was first installed, - and this MAC address is different each time the - instance boots. You should alter the following - files: - - - Replace - /etc/udev/rules.d/70-persistent-net.rules - with an empty file (contains network persistence - rules, including MAC address). - - - Replace - /lib/udev/rules.d/75-persistent-net-generator.rules - with an empty file (this generates the file - above). - - - Remove the HWADDR line from - /etc/sysconfig/network-scripts/ifcfg-eth0 - on Fedora-based images. - - - - 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. - -
-
- Ensure ssh server runs - 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. -
-
- Disable firewall - 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. -
-
- Access instance by using ssh public key - (cloud-init) - 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. - If both the XenAPI agent and cloud-init are - present in an image, cloud-init handles ssh-key - injection. The system assumes cloud-init is - present when the image has the cloud_init_installed - property. - - Use <package>cloud-init</package> to fetch the - public key - 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. - 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: - user: admin - - - Write a custom script to fetch the public - key - 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. - 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. - if [ ! -d /root/.ssh ]; then - mkdir -p /root/.ssh - chmod 700 /root/.ssh -fi - -# Fetch public key using HTTP -ATTEMPTS=30 -FAILED=0 -while [ ! -f /root/.ssh/authorized_keys ]; do - curl -f http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key > /tmp/metadata-key 2>/dev/null - if [ $? -eq 0 ]; then - cat /tmp/metadata-key >> /root/.ssh/authorized_keys - chmod 0600 /root/.ssh/authorized_keys - restorecon /root/.ssh/authorized_keys - rm -f /tmp/metadata-key - echo "Successfully retrieved public key from instance metadata" - echo "*****************" - echo "AUTHORIZED KEYS" - echo "*****************" - cat /root/.ssh/authorized_keys - echo "*****************" - else - FAILED=`expr $FAILED + 1` - if [ $FAILED -ge $ATTEMPTS ]; then - echo "Failed to retrieve public key from instance metadata after $FAILED attempts, quitting" - break - fi - echo "Could not retrieve public key from instance metadata (attempt #$FAILED/$ATTEMPTS), retrying in 5 seconds..." - sleep 5 - fi -done - - 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. - - - - - -
-
- Process user data and other metadata - (cloud-init) - In addition to the ssh public key, an image might need - additional information from OpenStack, such as Provide user data to instances, that the user - submitted when requesting the image. For example, you might - want to set the host name of the instance when it is booted. - Or, you might wish to configure your image so that it executes - user data content as a script on boot. - You can access this information through the metadata - service or referring to Store metadata on the configuration drive. As the OpenStack metadata - service is compatible with version 2009-04-04 of the - Amazon EC2 metadata service, consult the Amazon EC2 - documentation on Using Instance Metadata for details on how to - retrieve user data. - - 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. -
-
- Ensure image writes boot log to console - 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. - 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: - linux /boot/vmlinuz-3.2.0-49-virtual root=UUID=6d2231e4-0975-4f35-a94f-56738c1a8150 ro console=ttyS0 - 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: - GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" - Next, update the grub configuration. On Debian-based - operating-systems such as Ubuntu, run this command: - # update-grub - On Fedora-based systems, such as RHEL and CentOS, and on - openSUSE, run this command: - # grub2-mkconfig -o /boot/grub2/grub.cfg -
-
- Paravirtualized Xen support in the kernel (Xen - hypervisor only) - Prior to Linux kernel version 3.0, the mainline branch - of the Linux kernel did not have support for paravirtualized - Xen virtual machine instances (what Xen calls DomU - guests). If you are running the Xen hypervisor with - paravirtualization, and you want to create an image for an - older Linux distribution that has a pre 3.0 kernel, you - must ensure that the image boots a kernel that has been - compiled with Xen support. -
-
- Manage the image cache - 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. - For information about libvirt images in OpenStack, see - The life of an OpenStack libvirt image from Pádraig - Brady. - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Image cache management configuration - options
Configuration option=Default value(Type) Description
preallocate_images=none(StrOpt) VM image preallocation - mode: - - none. No - storage provisioning occurs up - front. - - - 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. - -
remove_unused_base_images=True(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.
remove_unused_original_minimum_age_seconds=86400(IntOpt) Unused unresized base images younger - than this are not removed. Default is 86400 - seconds, or 24 hours.
remove_unused_resized_minimum_age_seconds=3600(IntOpt) Unused resized base images younger - than this are not removed. Default is 3600 - seconds, or one hour.
- To see how the settings affect the deletion of a running - instance, check the directory where the images are - stored: - # ls -lash /var/lib/nova/instances/_base/ - In the /var/log/compute/compute.log - file, look for the identifier: - 2012-02-18 04:24:17 41389 WARNING nova.virt.libvirt.imagecache [-] Unknown base file: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810 -a0d1d5d3_20 -2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removable base files: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810 -a0d1d5d3 /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810a0d1d5d3_20 -2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removing base file: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810a0d1d5d3 - 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. -
- diff --git a/doc/image-guide/figures/centos-complete.png b/doc/image-guide/figures/centos-complete.png deleted file mode 100644 index 2e42118a44..0000000000 Binary files a/doc/image-guide/figures/centos-complete.png and /dev/null differ diff --git a/doc/image-guide/figures/centos-install.png b/doc/image-guide/figures/centos-install.png deleted file mode 100644 index f0c6f39298..0000000000 Binary files a/doc/image-guide/figures/centos-install.png and /dev/null differ diff --git a/doc/image-guide/figures/centos-tcpip.png b/doc/image-guide/figures/centos-tcpip.png deleted file mode 100644 index 1d81f0a09c..0000000000 Binary files a/doc/image-guide/figures/centos-tcpip.png and /dev/null differ diff --git a/doc/image-guide/figures/freebsd-partitions.png b/doc/image-guide/figures/freebsd-partitions.png deleted file mode 100644 index 2e5f49dbbb..0000000000 Binary files a/doc/image-guide/figures/freebsd-partitions.png and /dev/null differ diff --git a/doc/image-guide/figures/install-method.png b/doc/image-guide/figures/install-method.png deleted file mode 100644 index 572cd0c328..0000000000 Binary files a/doc/image-guide/figures/install-method.png and /dev/null differ diff --git a/doc/image-guide/figures/ubuntu-finished.png b/doc/image-guide/figures/ubuntu-finished.png deleted file mode 100644 index c60c9a7cbf..0000000000 Binary files a/doc/image-guide/figures/ubuntu-finished.png and /dev/null differ diff --git a/doc/image-guide/figures/ubuntu-grub.png b/doc/image-guide/figures/ubuntu-grub.png deleted file mode 100644 index a672ccb1ba..0000000000 Binary files a/doc/image-guide/figures/ubuntu-grub.png and /dev/null differ diff --git a/doc/image-guide/figures/ubuntu-install.png b/doc/image-guide/figures/ubuntu-install.png deleted file mode 100644 index 3d757828fa..0000000000 Binary files a/doc/image-guide/figures/ubuntu-install.png and /dev/null differ diff --git a/doc/image-guide/figures/ubuntu-software-selection.png b/doc/image-guide/figures/ubuntu-software-selection.png deleted file mode 100644 index 1258e7bbe4..0000000000 Binary files a/doc/image-guide/figures/ubuntu-software-selection.png and /dev/null differ diff --git a/doc/image-guide/figures/url-setup.png b/doc/image-guide/figures/url-setup.png deleted file mode 100644 index 40b745047b..0000000000 Binary files a/doc/image-guide/figures/url-setup.png and /dev/null differ diff --git a/doc/image-guide/figures/virt-manager-new.png b/doc/image-guide/figures/virt-manager-new.png deleted file mode 100644 index 95c5203111..0000000000 Binary files a/doc/image-guide/figures/virt-manager-new.png and /dev/null differ diff --git a/doc/image-guide/locale/fr.po b/doc/image-guide/locale/fr.po deleted file mode 100644 index a2d8966be0..0000000000 --- a/doc/image-guide/locale/fr.po +++ /dev/null @@ -1,2614 +0,0 @@ -# Translators: -# Andreas Jaeger , 2015 -# Frédéric , 2014 -# Katerina Katapodi , 2015 -# Nicolas HAHN , 2014 -# Tom Fifield , 2015 -# -# -# OpenStack Infra , 2015. #zanata -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-23 04:52+0000\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-09-03 09:51+0000\n" -"Last-Translator: openstackjenkins \n" -"Language: fr\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" -"X-Generator: Zanata 3.7.1\n" -"Language-Team: French\n" - -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 "" -"(BoolOpt) Est-ce que les images de base inutilisées doivent être enlevées? " -"Lorsque configuré à True, l'intervalle auquel les images de base sont " -"enlevées est configuré avec les deux réglages suivant. Si configuré à False " -"les images de base ne sont jamais enlevées par Compute." - -msgid "" -"(IntOpt) Unused resized base images younger than this are not removed. " -"Default is 3600 seconds, or one hour." -msgstr "" -"(IntOpt) Les images de base non redimensionnées inutilisées plus récentes " -"que celle-ci sont enlevées. Par défaut, réglé sur 3600 seconds, soit 1 heure." - -msgid "" -"(IntOpt) Unused unresized base images younger than this are not removed. " -"Default is 86400 seconds, or 24 hours." -msgstr "" -"(IntOpt) Les images de base non redimensionnées inutilisées plus récentes " -"que celle-ci ne sont pas enlevées. Par défaut, réglé sur 86400 seconds, soit " -"24 heures. " - -msgid "(StrOpt) VM image preallocation mode:" -msgstr "(StrOpt) mode de pré-allocation d'image VM:" - -msgid "(Type) Description" -msgstr "(Type) Description" - -msgid "..." -msgstr "..." - -msgid "2013" -msgstr "2013" - -msgid "2014" -msgstr "2014" - -msgid "2015" -msgstr "2015" - -msgid "aki. An Amazon kernel image." -msgstr "aki. Une image de kernel Amazon." - -msgid "ami. An Amazon machine image." -msgstr "ami. Une image de machine Amazon." - -msgid "ari. An Amazon ramdisk image." -msgstr "ari. Une image disque RAM Amazon." - -msgid "" -"auto_disk_config=True is set as a property on the image " -"in the image registry." -msgstr "" -"auto_disk_config=True est configuré en tant que propriété " -"sur l'image dans le registre d'image." - -msgid "" -"bare. The image does not have a container or metadata " -"envelope." -msgstr "" -"bare. L'image ne possède pas de conteneur ou d'enveloppe " -"de métadonnées." - -msgid "none. No storage provisioning occurs up front." -msgstr "" -"none. Aucune allocation de capacité de stockage initiale." - -msgid "ovf. The OVF container format." -msgstr "ovf. Le format de conteneur OVF." - -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 "" -" ne monte pas l'image directement dans le système de " -"fichiers local. Il vous donne une interface shell vous permettant de voir, " -"éditer, et supprimer les fichiers. La plupart des commandes , comme , , et , sont " -"similaires aux commandes bash traditionnelles." - -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 "" -"Nous désirons éditer le fichier ifcfg-eth0 pour y enlever la ligne HWADDR. La commande " -" va copier le fichier sur l'hôte, invoquer votre éditeur, et " -"recopier le fichier." - -#. 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. -msgid "" -"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" -msgstr "" -"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" - -#. 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. -msgid "" -"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" -msgstr "" -"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" - -#. 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. -msgid "" -"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" -msgstr "" -"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" - -#. 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. -msgid "" -"@@image: 'figures/freebsd-partitions.png'; " -"md5=47dbba18dda83b095f370a71e1dc3413" -msgstr "" -"@@image: 'figures/freebsd-partitions.png'; " -"md5=47dbba18dda83b095f370a71e1dc3413" - -#. 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. -msgid "" -"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" -msgstr "" -"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" -msgstr "" -"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" -msgstr "" -"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-software-selection.png'; " -"md5=423be828f701345f7d20551a39f24271" -msgstr "" -"@@image: 'figures/ubuntu-software-selection.png'; " -"md5=423be828f701345f7d20551a39f24271" - -#. 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. -msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" -msgstr "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" - -msgid "" -"A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains " -"an AMI file, AKI file, and ARI file." -msgstr "" -"Un tarball UEC (Cloud Entreprise ubuntu) est un fichier tarball gzippé " -"contenant un fichier AMI, un fichier AKI, et un fichier ARI." - -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 "" -"Un fichier kernel que l'hyperviseur va initialement charger pour booter " -"l'image. Pour une machine Linux, cela serait un fichier vmlinuz." - -msgid "" -"A virtual machine image is a single file which contains a virtual disk that " -"has a bootable operating system installed on it." -msgstr "" -"Une image de machine virtuelle est un fichier unique qui contient un disque " -"virtuel sur lequel est installé un système d'exploitation bootable." - -msgid "AKI (Amazon Kernel Image)" -msgstr "AKI (Image de Kernel Amazon Kernel)" - -msgid "AMI (Amazon Machine Image):" -msgstr "AMI (Image de Machine Amazon Machine):" - -msgid "AMI/AKI/ARI" -msgstr "AMI/AKI/ARI" - -msgid "ARI (Amazon Ramdisk Image)" -msgstr "ARI (Image Ram-disque Amazon)" - -msgid "" -"Accept the default keymap or select an appropriate mapping for your needs." -msgstr "" -"Acceptez la disposition du clavier par défaut ou sélectionnez une " -"disposition appropriée pour vos besoins." - -msgid "Accept the default network mirror." -msgstr "Acceptez le miroir réseau par défaut." - -msgid "Access instance by using ssh public key (cloud-init)" -msgstr "Accéder à l'instance en utilisant une clé publique ssh (cloud-init)" - -msgid "Access instance using ssh public key (cloud-init)" -msgstr "" -"Accès à l'instance en utilisant une clé ssh publique (cloud-init)" - -msgid "" -"After you exit, you can open a shell to complete manual configuration steps. " -"Select Yes to make a few OpenStack-specific changes:" -msgstr "" -"Après que vous ayez quitté, vous pouvez ouvrir un shell pour compléter les " -"étapes de configuration manuelles. Sélectionnez Yes " -"pour faire des changements spécifiques OpenStack:" - -msgid "" -"All associated properties for an image can be displayed using the " -" command. For example:" -msgstr "" -"Toutes les propriétés associées pour une image peuvent être affichées en " -"utilisant la commande . Par exemple:" - -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 "" -"Un package OVF peut être distribué de différentes manières. Par exemple, il " -"pourrait être distribué sous la forme d'un jeu de fichiers discrets, ou en " -"tant que fichier d'archive tar avec une extension .ova ( appliance/" -"application virtuelle ouverte)." - -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 "" -"Un cloud de calcul OpenStack n'est pas très utile à moins que vous ayez des " -"images de machine virtuelle (que certains appellent \"appliances virtuelles" -"\"). Ce guide décrit comment obtenir, créer, et modifier des images de " -"machine virtuelle qui sont compatibles avec OpenStack." - -msgid "" -"An instance must interact with the metadata service to perform several tasks " -"on start up. For example, the instance must get the ssh public key and run " -"the user data script. To ensure that the instance performs these tasks, use " -"one of these methods:" -msgstr "" -"Une instance doit interagir avec le service de métadonnées pour accomplir " -"plusieurs tâches au démarrage. Par exemple, l'instance doit obtenir la clé " -"publique ssh et lancer le script de données utilisateur. Pour s'assurer que " -"l'instance réalise ces tâches, utilisez l'une de ces méthodes:" - -msgid "" -"An optional ramdisk file mounted at boot time. For a Linux machine, this " -"would be an initrd file." -msgstr "" -"Un fichier ram-disque optionnel monté lors du boot. Pour une machine Linux, " -"cela serait un fichier initrd." - -msgid "Argument to qemu-img" -msgstr "Argument de qemu-img" - -msgid "" -"As of this writing, we are not aware of other distributions that provide " -"images for download." -msgstr "" -"Au moment où nous écrivons ces lignes, nous n'avons pas connaissance " -"d'autres distributions qui fourniraient des images en téléchargement." - -msgid "" -"Assume that the name of your virtual machine image is ubuntu-14.04, which you need to know when you use commands to " -"manipulate the state of the image." -msgstr "" -"En considérant que le nom de votre image de machine virtuelle est " -"ubuntu-14.04, et qu'il vous est nécessaire de connaitre " -"lorsque vous utilisez les commandes pour manipuler l'état " -"de l'image." - -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 "" -"Nous considérons ici que vous avec une image qcow2 CentOS appelée " -"centos63_desktop.img. Montez l'image en mode lecture-" -"écriture en tant que root, comme suit:" - -msgid "Assume that:" -msgstr "Considérons que:" - -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 "" -"Considérant que le premier périphérique bloc (/dev/nbd0) n'est pas en cours d'utilisation, nous pouvons exposer les " -"partitions du disque en utilisant les commandes et " -". En tant que root:" - -msgid "" -"At the initial Installer boot menu, choose the Install or upgrade " -"an existing system option. Step through the installation prompts. " -"Accept the defaults." -msgstr "" -"Dans le menu d'installation au boot, choisissez l'option Installer " -"ou mettre à jour un système existant. Suivez et répondez aux " -"différentes étapes d'installation. Acceptez les choix par défaut." - -msgid "" -"At the initial Installer boot menu, choose the Install " -"option. Step through the install prompts, the defaults should be fine." -msgstr "" -"Lorsque le menu initial de l'installeur apparaît, choisissez l'option " -"Installer. Complétez les informations demandées lors " -"des étapes d'installation, les choix par défaut devraient convenir." - -msgid "Automatic updates" -msgstr "Mises à jour automatiques" - -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 "" -"Puisque 86400 secondes (24 heuhres) est le temps par défaut pour " -"remove_unused_original_minimum_age_seconds, vous pouvez " -"soit attendre pour que l'image de base soit enlevée à l'issue de cet " -"intervalle de temps, soit régler cette valeur à un intervalle de temps plus " -"court dans nova.conf. Redémarrez tous les services nova " -"après avoir modifié un réglage dans nova.conf." - -msgid "" -"Because raw images don't support snapshots, OpenStack Compute will " -"automatically convert raw image files to qcow2 as needed." -msgstr "" -"Puisque les images raw ne supportent pas les copies instantanées, OpenStack " -"Calcul va automatiquement convertir les fichiers d'image raw en qcow2 au " -"besoin." - -msgid "" -"Because the default does not work, you must select manual partitioning. The " -"partition editor should list only one block device. If you use virtio for " -"the disk device driver, it is named vtbd0. Select this " -"device and run the command three times:" -msgstr "" -"Puisque le réglage par défaut ne fonctionne pas, vous devez sélectionner un " -"partitionnement manuel. L'éditeur de partition devrait lister uniquement un " -"périphérique bloc. Si vous utilisez virtio pour le driver du périphérique " -"disque, il est appelé vtbd0. Sélectionnez ce périphérique " -"et lancez la commande trois fois:" - -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 "" -"Avant de démarrer une machine virtuelle avec libvirt, vérifiez que le réseau " -"\"default\" de libvirt a été démarré. Ce réseau doit être actif pour que " -"votre machine virtuelle soit en mesure de se connecter en-dehors du réseau. " -"Démarrer ce réseau va créer un pont Linux (habituellement appelé " -"virbr0), des règles iptables, et un process dnsmasq qui " -"servira de serveur DHCP." - -msgid "" -"By using the same hypervisor, you can ensure that you emulate the same " -"devices that exist in production. However, if you use full hardware " -"virtualization instead of paravirtualization, you do not need to use the " -"same hypervisor; you must use the same type of virtualized hardware because " -"FreeBSD device names are related to their drivers. If the name of your root " -"block device or primary network interface in production differs than the " -"names used during image creation, errors can occur." -msgstr "" -"En utilisant le même hyperviseur, vous pouvez vous assurer que vous émulerez " -"les même périphériques qui existent en production. Cependant, si vous " -"utilisez une virtualisation matérielle complète au lieu de la para-" -"virtualisation, vous n'avez pas besoin d'utiliser le même hyperviseur; vous " -"devez utiliser le me type de matériel virtualisé car les noms des " -"périphériques FreeBSD sont relatifs à leurs drivers. Si le nom de votre " -"périphérique bloc racine ou interface de réseau primaire en production " -"diffère des noms utilisés durant la création de l'image, des erreurs peuvent " -"survenir." - -msgid "CentOS directory: centos/6/os/x86_64" -msgstr "Dossier CentOS: centos/6/os/x86_64" - -msgid "Choose URL as the installation method." -msgstr "Choisissez URL en tant que méthode d'installation." - -msgid "CirrOS (test) images" -msgstr "Images CirrOS (test)" - -msgid "Clean up (remove MAC address details)" -msgstr "Nettoyage (enlever les informations d'adresse MAC)" - -msgid "Clean up when you're done:" -msgstr "Nettoyez lorsque vous avez terminé:" - -msgid "" -"Click one of the HTTP links in the right-hand column next " -"to one of the mirrors." -msgstr "" -"Cliquez sur un des liens HTTP dans la colonne de droite à " -"côté d'un des miroirs." - -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 "" -"Cliquez sur le bouton \"Nouveau\" en haut à gauche et suivez les " -"instructions.Il vous sera montré une série de boites de " -"dialogue qui vous permettront d'indiquer des informations à propos de la " -"machine virtuelle." - -msgid "Click the isos/ folder link." -msgstr "Cliquez sur le lien de dossier isos/." - -msgid "Click the x86_64/ folder link for 64-bit images." -msgstr "" -"Cliquez sur le lien de dossier x86_64/ pour les images 64-" -"bits." - -msgid "" -"Click the folder link of the CentOS version that you want to use. For " -"example, 6.4/." -msgstr "" -"Cliquez sur le lien de dossier de la version CentOS que vous souhaitez " -"utiliser. Par exemple, 6.4/." - -msgid "" -"Click the netinstall ISO image that you want to download. For example, " -"CentOS-6.4-x86_64-netinstall.iso is a good choice " -"because it is a smaller image that downloads missing packages from the " -"Internet during installation." -msgstr "" -"Cliquez sur l'image ISO netinstall que vous souhaitez télécharger. Par " -"exemple, CentOS-6.4-x86_64-netinstall.iso est un bon " -"choix car c'est une image plus petite qui télécharge les packages manquant à " -"partir d'Internet durant l'installation." - -msgid "" -"Complete the VirtIO drivers installation by running the following command:" -msgstr "" -"Compléter l'installation des pilotes VirtIO en exécutant la commande " -"suivante :" - -msgid "Configuration option=Default value" -msgstr "Option de configuration=Valeur par défaut" - -msgid "Configure TCP/IP" -msgstr "Configurez TCP/IP" - -msgid "Configure console" -msgstr "Configurer la console" - -msgid "" -"Configure the primary network interface to use DHCP. In this example, which " -"uses a virtio network device, this interface is named vtnet0." -msgstr "" -"Configurez l'interface primaire de réseau pour utiliser DHCP. Dans cet " -"exemple, qui utilise un périphérique réseau virtio, cette interface est " -"appelée vtnet0." - -msgid "Configure to fetch metadata" -msgstr "Configuration pour prendre les métadonnées" - -msgid "" -"Consider using other mirrors as an alternative to mirror.umd.edu." -msgstr "" -"Vous pouvez utiliser d'autres miroirs que mirror.umd.edu." - -msgid "Container formats" -msgstr "Formats de conteneur" - -msgid "Converting between image formats" -msgstr "Conversion entre formats d'image" - -msgid "" -"Converting images from one format to another is generally straightforward." -msgstr "" -"Convertir des images d'un format à un autre est généralement sans difficulté." - -msgid "Create a 15GB qcow2 image:" -msgstr "Créer une image qcow2 de 15 Go : " - -msgid "" -"Create a new LVM partition with the additional space. For example, " -"." -msgstr "" -"Créer une nouvelle partition LVM avec l'espace supplémentaire. Par exemple, " -"." - -msgid "Create a new physical volume. For example, ." -msgstr "Créer un nouveau volume physique. Par exemple, ." - -msgid "Create images manually" -msgstr "Créer des images manuellement" - -msgid "Create two partitions:" -msgstr "Créez deux partition:" - -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 "" -"La création d'une nouvelle image est une étape réalisée en-dehors de votre " -"installation OpenStack. Vous créez la nouvelle image manuellement sur votre " -"propre système et vous envoyez l'image à votre cloud." - -msgid "Detach the CD-ROM and reboot" -msgstr "Détachez le CD-ROM et rebootez" - -msgid "" -"Detect if any additional space is available on the disk. For example, parse " -"the output of ." -msgstr "" -"Détecter si un espace supplémentaire est disponible sur le disque. Par " -"exemple, interprétez la sortie de ." - -msgid "Disable firewall" -msgstr "Firewall désactivé" - -msgid "Disable the zeroconf route" -msgstr "Désactiver la route zeroconf" - -msgid "Disk and container formats for images" -msgstr "Formats de disque et de conteneur pour les images" - -msgid "Disk formats" -msgstr "Formats de disque" - -msgid "" -"Disk partitioning is a critical element of the image creation process and " -"the auto-generated default partitioning scheme does not work with " -"bsd-cloudinit at this time." -msgstr "" -"Le partitionnement du disque est un élément crucial du processus de création " -"d'image et le schéma de partitionnement auto-généré par défaut ne fonctionne " -"pas avec bsd-cloudinit pour le moment." - -msgid "" -"Disk partitions and resize root partition on boot (cloud-init)" -msgstr "" -"Partitions disque et redimensionnement de la partition racine lors du boot " -"(cloud-init)" - -msgid "Disk partitions and resize root partition on boot (cloud-init)" -msgstr "" -"Partitions disque et redimensionnement de la partition racine au boot (cloud-" -"init)" - -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 "" -"Ne tentez pas d'utiliser ces outils pour modifier une image qui est attachée " -"à une machine virtuelle en fonctionnement. Ces outils sont conçus pour " -"modifier les images qui ne sont pas en fonctionnement uniquement." - -msgid "Download a CentOS install ISO" -msgstr "Téléchargez une ISO d'installation de CentOS" - -msgid "Download an Ubuntu install ISO" -msgstr "Téléchargement d'un ISO d'installation Ubuntu" - -msgid "Download and install Cloudbase-Init:" -msgstr "Télécharger et installer Cloudbase-Init :" - -msgid "Enable the VirtIO drivers." -msgstr "Activer les pilotes VirtIO." - -msgid "Ensure image writes boot log to console" -msgstr "S'assurer que l'image écrive le journal de démarrage sur la console" - -msgid "Ensure ssh server runs" -msgstr "Assurez-vous que le serveur ssh fonctionne." - -msgid "Example guestfish session" -msgstr "Exemple de session guestfish" - -msgid "Example: CentOS image" -msgstr "Exemple: image CentOS" - -msgid "Example: FreeBSD image" -msgstr "Exemple: image FreeBSD" - -msgid "Example: Microsoft Windows image" -msgstr "Exemple: image Microsoft Windows" - -msgid "Example: Ubuntu image" -msgstr "Exemple: image Ubuntu" - -msgid "" -"Extend the logical volume contained the root partition by the amount of " -"space. For example, ." -msgstr "" -"Etendre le volume logique contenu dans la partition racine par la quantité " -"d'espace. Par exemple, ." - -msgid "" -"Extend the volume group with this physical partition. For example, " -"." -msgstr "" -"2tendre le groupe de volumes avec cette partition physique. Par exemple, " -"." - -msgid "Final config" -msgstr "Configuration finale" - -msgid "First partition: A 64kB freebsd-boot partition with no mount point." -msgstr "" -"Première partition: une partition de boot freebsd de 64 ko sans point de " -"montage." - -msgid "" -"For example, to mount the root partition from our centos63_desktop." -"qcow2 image to /mnt, we can do:" -msgstr "" -"Par exemple, pour monter la partition root à partir de notre image " -"centos63_desktop.qcow2 sur /mnt, " -"nous pouvons faire:" - -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 "" -"Pour certain types de changements, vous pourrez trouver plus aisé de monter " -"le système de fichiers de l'image directement dans le client. le programme " -", provenant aussi du projet libguestfs, vous permet de le " -"faire." - -msgid "" -"For the command to work properly on CentOS 6." -"x, you might need to add the following lines to " -"the /boot/grub/menu.lst file:" -msgstr "" -"Pour que la commande fonctionne correctement sur CentOS 6." -"x, il peut être nécessaire d'ajouter les ligne " -"suivantes au fichier /boot/grub/menu.lst:" - -msgid "" -"For the instance to access the metadata service, you must disable the " -"default zeroconf route:" -msgstr "" -"Pour que l'instance puisse accéder au service de métadonnées, vous devez " -"désactiver la route par défaut zeroconf:" - -msgid "" -"FreeBSD 9.2 does not support peer-verification for https. " -"For FreeBSD 9.2, run this command:" -msgstr "" -"FreeBSD 9.2 ne supporte pas la vérification des points pour " -"https. Pour FreeBSD 9.2, lancez cette commande:" - -msgid "From inside the instance, as root:" -msgstr "Depuis l'intérieur de l'instance, en tant que root:" - -msgid "" -"From the list of services to start on boot, you must select ssh. Optionally, select other services." -msgstr "" -"A partir de la liste de services à démarrer au boot, vous devez sélectionner " -"ssh. Optionnellement, " -"sélectionnez d'autres services." - -msgid "Get images" -msgstr "Obtenir les images" - -msgid "Get the installer ISO:" -msgstr "Obtenir l'ISO de l'installeur:" - -msgid "Go further with guestfish" -msgstr "Aller plus loin avec guestfish" - -msgid "Hostname" -msgstr "Nom d'Hôte" - -msgid "ISO" -msgstr "ISO" - -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 "" -"Si console=ttyS0 n'apparaît pas, vous devez modifier " -"votre configuration grub. En général, vous ne devriez pas mettre à jour le " -"fichier grub.cfg directement, puisqu'il est généré de " -"façon automatique. A la place, vous devriez éditer /etc/default/" -"grub et modifier la valeur de la variable " -"GRUB_CMDLINE_LINUX_DEFAULT:" - -msgid "" -"If prompted about which type of devices your installation uses, choose " -"Basic Storage Devices." -msgstr "" -"Si le type de périphériques que votre installation utilise vous est demandé, " -"choisissez Périphériques de Stockage de Base." - -msgid "" -"If the account you use to ssh into your server does not have permissions to " -"run libvirt, but has sudo privileges, do:" -msgstr "" -"Si le compte que vous utilisez pour faire du ssh à l'intérieur de votre " -"serveur ne dispose pas des permissions pour lancer libvirt, mais dispose par " -"contre des privilèges sudo, faites: " - -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 "" -"Si l'image a des partitions multiples, utilisez pour " -"exposer les partitions en tant que périphériques séparés (par exemple, " -"/dev/mapper/loop0p1), puis montez la partition qui " -"correspond au système de fichier racine:" - -msgid "" -"If the image has, say three partitions (/boot, /, swap), there should be one " -"new device created for each partition:" -msgstr "" -"Si l'image a, disons trois partitions (/boot, /, swap), il devrait y avoir " -"un périphérique créé pour chacune d'entre elles:" - -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 "" -"Si l'image a, disons trois partitions (/boot, /, swap), il devrait y avoir " -"un périphérique créé par partition:Pour monter la seconde " -"partition, en tant que root:Une fois ceci fait, pour " -"nettoyer:" - -msgid "" -"If the image only has a single partition, you can mount the loop device " -"directly:" -msgstr "" -"Si l'image a seulement une partition unique, vous pouvez monter le " -"périphérique de boucle directement:" - -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 "" -"Si les partitions de l'image sont gérées avec LVM, après avoir utilisé " -" et , vous devez utiliser " -"et afin d'exposer les partitions LVM en tant que " -"périphériques pouvant être montés:" - -msgid "" -"If the image partitions are not managed with LVM, they can be mounted " -"directly:" -msgstr "" -"Si les partitions de l'image ne sont pas gérées par LVM, elles peuvent être " -"montées directement:" - -msgid "" -"If the installer asks for web site name and CentOS directory separately, you " -"might enter:" -msgstr "" -"Si l'installeur demande un nom de site web et un dossier CentOS séparément, " -"vous pourriez entrer:" - -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 "" -"Si le périphérique de bloc réseau que vous avez sélectionné est déjà en " -"cours d'usage, la commande initiale échouera de façon " -"silencieuse, et les fichiers de périphérique /dev/nbd3p{1,2,3} ne seront pas créés." - -msgid "If the network is not active, start it by doing:" -msgstr "Si le réseau n'est pas actif, lancez-le en faisant:" - -msgid "" -"If unsure, use the default partition scheme for the installer because no " -"scheme is better than another." -msgstr "" -"Si vous n'êtes pas sûr, utilisez le schéma de partitionnement par défaut " -"pour l'installeur car aucun schéma n'est mieux qu'un autre." - -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 "" -"Si vous n'êtes pas sûr, nous vous recommandons d'utiliser le schéma de " -"partitionnement par défaut proposé par l'installeur, puisqu'il n'y a pas " -"d'avantage clair à choisir un schéma par rapport à un autre." - -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 "" -"Si nous ne pouvons pas savoir à l'avance quel est le point de montage dans " -"le client, nous pouvons utiliser le drapeau -i(inspect) " -"pour indiquer à guestmount de déterminer automatiquement quel point de " -"montage utiliser:Une fois monté, nous pouvons faire des " -"choses comme lister les packages installés en utilisant rpm: " -"Une fois ceci fait, nous démontons:" - -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 "" -"Si vous construisez l'image sur un serveur sans serveur graphique, et que " -"vous avez un serveur X sur votre machine locale, vous pouvez lancer " -" en utilisant le transfert X11 ssh pour accéder à " -"l'interface graphique. Puisque virt-manager interagit directement avec " -"libvirt, il vous sera nécessaire d'être administrateur pour y accéder. Si " -"vous pouvez vous connecter en ssh en tant que root directement (ou avec un " -"utilisateur qui possède les permissions lui permettant d'interagir avec " -"libvirt), faites:" - -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 "" -"Si vous n'êtes pas en mesure ou si vous ne souhaitez pas installer " -"cloud-init à l'intérieur de l'invité, vous pouvez écrire " -"un script personnalisé pour prendre la clé publique et l'ajouter à un compte " -"utilisateur." - -msgid "" -"If you are using , the commands should look something like " -"this:" -msgstr "" -"Si vous utilisez , les commandes devraient ressembler à " -"quelque chose comme ça:" - -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 "" -"Si vous pouvez installer les packages cloud-utils et cloud-init, nous recommandons que lorsque vous créez vos images, vous créez " -"une partition unique ext3 ou ext4 (non gérée par LVM)." - -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 "" -"Si vous ne pouvez pas installer cloud-init et " -"cloud-tools à l'intérieur de votre invité, et que vous " -"souhaitez supporter le redimensionnement, vous devez écrire un script que " -"votre image lancera au démarrage pour modifier la table de partitions. Dans " -"ce cas, nous recommandons l'utilisation de LVM pour gérer vos partitions. En " -"raison d'une limitation du kernel Linux (au moment où ces lignes sont " -"écrites), vous ne pouvez pas modifier une table de partitions d'un disque " -"raw dont les partitions sont actuellement montées, mais vous pouvez le faire " -"pour LVM." - -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 "" -"Si vous supprimez les fichiers de règles de persistence du réseau, il est " -"possible que vous obteniez un message d'avertissement du kernel à propos " -"d'udev au démarrage, c'est la raison pour laquelle nous recommandons de les " -"remplacer par des fichiers vides." - -msgid "" -"If you do not use LVM, you must modify the table to extend the existing root " -"partition to encompass this additional space." -msgstr "" -"Si vous n'utilisez pas LVM, vous devez modifier la table afin d'étendre la " -"partition racine existante pour inclure cet espace supplémentaire." - -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 "" -"Si vous ne souhaitez pas utiliser virt-manager (par exemple, vous ne voulez " -"pas installer les dépendances sur votre serveur, vous n'avez pas de serveur " -"X qui tourne localement, le transfert X11 à travers SSH ne fonctionne pas), " -"vous pouvez utiliser l'outil pour démarrer la machine " -"virtuelle au travers de libvirt et vous connecter à la console graphique à " -"partir d'un client VNC installé sur votre machine locale." - -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 "" -"Si vous n'avez pas accès à libguestfs, vous pouvez monter des systèmes de " -"fichiers d'image directement dans l'hôte en utilisant des périphériques de " -"boucle, kpartx, et des périphériques de bloc réseau." - -msgid "" -"If you modify this example, the root partition, which is mounted on " -"/, must be the last partition on the drive so that it " -"can expand at run time to the disk size that your instance type provides. " -"Also note that bsd-cloudinit currently has a hard-" -"coded assumption that this is the second partition." -msgstr "" -"Si vous modifiez cet exemple, la partition racine, qui est montée sur " -"/, doit être la dernière partition sur le disque afin " -"qu'elle puisse être étendue lors du fonctionnement à la taille du disque que " -"votre type d'instance fournit. Veuillez aussi noter que bsd-" -"cloudinit fait la supposition que c'est la seconde partition." - -msgid "" -"If you use , the commands should look something like this:" -msgstr "" -"Si vous utilisez , les commandes devraient ressembler à " -"quelque chose comme ça:" - -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 "" -"Si vous utilisez LVM, vous pouvez ajouter une nouvelle entrée LVM à la table " -"de partitions, créer un nouveau volume physique LVM, l'ajouter au groupe de " -"volumes, et étendre la partition logique avec le volume racine." - -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 "" -"Si vous utilisez le driver XenAPI OpenStack, le service de calcul ajuste " -"automatiquement la partition et le système de fichier pour votre instance au " -"démarrage. Un redimensionnement automatique survient si les conditions " -"suivantes sont toutes remplies:" - -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 "" -"Si vous voulez modifier cette image pour charger le kernel 8021q au boot, " -"vous devez créer un script exécutable dans le dossier /etc/" -"sysconfig/modules/. Vous pouvez utiliser la commande guestfish " -" pour créer un fichier vide, la commande " -"pour l'éditer, et la commande pour le rendre exécutable." -" Nous ajoutons la ligne suivante au fichier et nous le " -"sauvegardons:Puis on le rend exécutable: " - -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 "" -"Si votre image utilise grub2 en tant que chargeur de démarrage, il devrait y " -"avoir une ligne dans le fichier de configuration de grub. Par exemple, " -"/boot/grub/grub.cfg, qui devrait ressembler à quelque " -"chose comme ça:" - -msgid "Image cache management configuration options" -msgstr "Options de configuration de gestion du cache d'Image" - -msgid "Image format" -msgstr "Format d'Image" - -msgid "Image is complete" -msgstr "L'image est complète" - -msgid "Image metadata" -msgstr "Image metadata" - -msgid "" -"In a CirrOS image, the login account is cirros. The " -"password is cubswin:)" -msgstr "" -"Dans une image CirrOS, le compte de login est cirros. Le " -"mot de passe est cubswin:)" - -msgid "" -"In an Ubuntu cloud image, the login account is ubuntu." -msgstr "" -"Dans une image de cloud Ubuntu, le compte de login est ubuntu." - -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 "" -"En général, nous recommandons la désactivation de tout firewall à " -"l'intérieur de votre image et d'utiliser les groupes de sécurité OpenStack " -"pour restreindre l'accès aux instances. Ceci est en raison du fait qu'avoir " -"un firewall installé sur votre instance peut rendre plus difficile " -"l'investigation de problèmes réseau si vous ne pouvez pas vous connecter à " -"votre instance." - -msgid "" -"In the /var/log/compute/compute.log file, look for the " -"identifier:" -msgstr "" -"Dans le fichier /var/log/compute/compute.log, " -"recherchez l'identifiant:" - -msgid "" -"In the configuration options window, change the " -"following settings:" -msgstr "" -"Dans la fenêtre options configuration, changer les " -"paramètres suivants : " - -msgid "" -"In the example above, the guest centos-6.4 uses VNC " -"display :1, which corresponds to TCP port 5901. You should be able to connect a VNC client running on your local " -"machine to display :1 on the remote machine and step through the " -"installation process." -msgstr "" -"Dans l'exemple au-dessus, l'invité centos-6.4 utilise " -"l'écran VNC :1, qui correspond au port TCP 5901. Vous devriez être en mesure de connecter un client VNC lancé sur " -"votre machine locale pour afficher :1 sur la machine distante et passer à " -"l'étape du processus d'installation." - -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 "" -"Dans ce cas, il s'agit de la partition /dev/sda2 que " -"nous voulons redimensionner. Nous créons une nouvelle image qcow2 et nous " -"utilisons la commande pour écrire une copie redimensionnée " -"de l'original dans la nouvelle image: " - -msgid "" -"In this example, /dev/loop0 is free. Associate a loop " -"device with the raw image:" -msgstr "" -"Dans cet exemple, /dev/loop0 est libre. Associez un " -"périphérique de boucle avec l'image raw:" - -msgid "" -"Install sudo and configure the freebsd " -"user to have passwordless access:" -msgstr "" -"installez sudo et configurez l'utilisateur " -"freebsd pour obtenir un accès sans mot de passe:" - -msgid "Install GRUB boot loader" -msgstr "Installer le chargeur de démarrage GRUB" - -msgid "Install cloud-init" -msgstr "Installation de cloud-init" - -msgid "Install the cloud-init package:" -msgstr "Installation du package cloud-init:" - -msgid "Install the ACPI service" -msgstr "Installer le service ACPI" - -msgid "Introduction" -msgstr "Introduction" - -msgid "" -"KVM with virtio drivers is used as the virtualization platform because that " -"is the most widely used among OpenStack operators. If you use a different " -"platform for your cloud virtualization, use that same platform in the image " -"creation step." -msgstr "" -"KVM avec les drivers virtio est utilisé en tant que plateforme de " -"virtualisation car il est le plus largement utilisé parmi les opérateurs " -"openStack. Si vous utilisez une plateforme différente pour votre " -"virtualisation de cloud, utilisez cette même plateforme lors de l'étape de " -"création de l'image." - -msgid "" -"Launch a VM on your local workstation. Use the same hypervisor, virtual " -"disk, and virtual network drivers as you use in your production environment." -msgstr "" -"Lancez une VM sur votre station de travail locale. Utilisez le même " -"hyperviseur, disque virtuel, et drivers de réseau virtuel que dans votre " -"environnement de production." - -msgid "Log in as administrator and start a command window." -msgstr "" -"Se connecter en tant qu'administrateur et démarrer une fenêtre de commande." - -msgid "Log in to newly created image" -msgstr "Loguez-vous dans l'image nouvellement créée" - -msgid "Loop devices, kpartx, network block devices" -msgstr "" -"Les périphériques de boucle, kpartx, et les périphériques de bloc réseau" - -msgid "Make a virtual drive:" -msgstr "Créez un périphérique virtuel:" - -msgid "Manage the image cache" -msgstr "Gérer le cache d'image" - -msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." -msgstr "" -"Microsoft Hyper-V Utilise le format VHD (Disque Dur Virtuel) pour les images." - -msgid "Microsoft Windows images" -msgstr "Images Microsoft Windows" - -msgid "Minimize boot delay:" -msgstr "Minimiser le délai de boot:" - -msgid "" -"Modify /etc/rc.local to fetch desired information from " -"the metadata service, as described in the next section." -msgstr "" -"Modifiez /etc/rc.local pour prendre les informations " -"voulues depuis le service de métadonnées, comme décrit dans la section " -"suivante." - -msgid "Modify a single file inside of an image" -msgstr "Modifier un fichier unique à l'intérieur d'une image" - -msgid "Modify images" -msgstr "Modifier les images" - -msgid "Modify the partition table to make it aware of the additional space:" -msgstr "" -"Modifier la table de partitions pour qu'elle ait connaissance de l'espace " -"additionnel:" - -msgid "Mount a qcow2 image (with LVM)" -msgstr "Monter une image qcow2 (avec LVM)" - -msgid "Mount a qcow2 image (without LVM)" -msgstr "Monter une image qcow2 (sans LVM)" - -msgid "Mount a raw image (with LVM)" -msgstr "Monter une image raw (avec LVM)" - -msgid "Mount a raw image (without LVM)" -msgstr "Monter une image raw (sans LVM)" - -msgid "" -"Network adapter to configure: Red Hat VirtIO Ethernet Adapter" -msgstr "" -"Adaptateur réseau pour configurer : Red Hat VirtIO Ethernet " -"Adapter" - -msgid "" -"Next, update the grub configuration. On Debian-based operating-systems such " -"as Ubuntu, run this command:" -msgstr "" -"Ensuite, mettez à jour la configuration grub. Sur les systèmes " -"d'exploitation basés sur Debian comme ubuntu, lancez cette commande:" - -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 "" -"Ensuite, nous voulons supprimer un fichier. Nous pouvons utiliser la " -"commande guestfish , qui fonctionne de la même façon que " -"dans un shell traditionnel." - -msgid "" -"Next, you need to use the command to identify the LVM " -"volume groups and then to expose the volumes as devices:" -msgstr "" -"Ensuite, il vous sera nécessaire d'utiliser la commande " -"pour identifier les groupes de volume LVM et pour exposer " -"les volumes en tant que périphériques:" - -msgid "No hard-coded MAC address information" -msgstr "Aucune information d'adresse MAC codée en dur" - -msgid "" -"Non-Xen with cloud-init/cloud-tools: One ext3/ext4 partition (no LVM, no /" -"boot, no swap)" -msgstr "" -"Non Xen avec cloud-init/cloud-tools: une partition ext3/ext4 (pas de LVM, " -"pas de /boot, pas de swap)" - -msgid "" -"Non-Xen without cloud-init/cloud-tools: LVM" -msgstr "" -"Non Xen sans cloud-init/cloud-tools: " -"LVM" - -msgid "OVF" -msgstr "OVF" - -msgid "Official Fedora images" -msgstr "Images officielles Fedora" - -msgid "Official Red Hat Enterprise Linux images" -msgstr "Images officielles Red Hat Enterprise Linux" - -msgid "Official Ubuntu images" -msgstr "Images Ubuntu officielles" - -msgid "Official images from other Linux distributions" -msgstr "Images officielles pour d'autres distributions de Linux" - -msgid "Official openSUSE and SLES images" -msgstr "Images officielles openSUSE et SLES" - -msgid "" -"On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this " -"command:" -msgstr "" -"Sur les systèmes basés sur Fedora, comme RHEL et CentOS, et sur openSUSE, " -"lancez cette commande:" - -msgid "" -"Once the installation is completed, the VM restarts. Define a password for " -"the administrator when prompted." -msgstr "" -"Une fois l'installation terminée, les VM redémarre. Définir un mot de passe " -"pour l'administrateur dans l'invite de commande." - -msgid "OpenStack" -msgstr "OpenStack" - -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 "" -"OpenStack Calcul n’inclut actuellement pas le support des packages OVF, donc " -"il vous sera nécessaire d'extraire le(s) fichier(s) d'image à partir d'un " -"package OVF si vous souhaitez l'utiliser avec OpenStack." - -msgid "OpenStack Foundation" -msgstr "Fondation OpenStack" - -msgid "OpenStack Linux image requirements" -msgstr "Pré-requis pour image Linux OpenStack" - -msgid "OpenStack Virtual Machine Image Guide" -msgstr "Guide de l'Image de Machine Virtuelle OpenStack" - -msgid "Optionally, add users." -msgstr "Optionnellement, ajoutez des utilisateurs." - -msgid "Oz" -msgstr "Oz" - -msgid "Packer" -msgstr "Packer" - -msgid "" -"Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux " -"kernel version < 3.0)" -msgstr "" -"Support para-virtualisé Xen dans le kernel Linux (hyperviseur Xen seulement " -"à partir des versions < 3.0 du kernel Linux)" - -msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" -msgstr "Support Xen Para-virtualisé dans le kernel (Hyperviseur Xen seulement)" - -msgid "Partition the disks" -msgstr "Partitionner les disques" - -msgid "Point the installer to a CentOS web server" -msgstr "Pointez l'installeur sur un serveur web CentOS" - -msgid "Power off the system:" -msgstr "Eteignez le système:" - -msgid "Process user data and other metadata (cloud-init)" -msgstr "" -"Traitement des données utilisateur et autres métadonnées (cloud-" -"init)" - -msgid "Process user data and other metadata (cloud-init)" -msgstr "Traitement des données utilisateur et autres métadonnées (cloud-init)" - -msgid "" -"Provide a host name for your image. If you use bsd-cloudinit, it overrides this value with the name provided by OpenStack " -"when an instance boots from this image." -msgstr "" -"Fournissez un nom d'hôte pour votre image. Si vous utilisez bsd-" -"cloudinit, cela écrasera cette valeur avec le nom fourni par " -"OpenStack lorsqu'une instance boot à partir de cette image." - -msgid "Rackspace Cloud Builders (multiple distros) images" -msgstr "Images Rackspace Cloud Builders (distributions multiples)" - -msgid "Raw" -msgstr "Raw" - -msgid "Red Hat Enterprise Linux 6 KVM Guest Image" -msgstr "Image Invité KVM Red Hat Enterprise Linux 6" - -msgid "Red Hat Enterprise Linux 7 KVM Guest Image" -msgstr "Image Invité KVM Red Hat Enterprise Linux 7" - -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." - -msgid "Resize an image" -msgstr "Redimensionner une image" - -msgid "Resize the root file system. For example, ." -msgstr "" -"Redimensionner le système de fichiers racine. Par exemple, ." - -msgid "Resize the root volume file system." -msgstr "Redimensionner le système de fichiers du volume racine." - -msgid "" -"Run the command to see a range of allowed --os-" -"variant options." -msgstr "" -"Lancez la commande pour voir les options --os-" -"variant autorisées." - -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 "" -"Lancez les commandes suivantes à partir de l'hôte pour éjecter le disque et " -"rebootez en utilisant virsh, en tant que root. Si vous utilisez virt-" -"manager, les commandes ci-dessous fonctionneront, mais vous pouvez aussi " -"utiliser l'interface utilisateur graphique pour le détacher et le rebooter " -"en le stoppant et en le redémarrant manuellement." - -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 "" -"Lancez les commandes suivantes dans l'hôte en tant que root pour démarrer la " -"machine une fois de plus une fois mise en pause, éjectez le disque et " -"réveillez-la. Si vous utilisez virt-manager, vous pouvez utiliser " -"l'interface utilisateur graphique à la place." - -msgid "" -"Run the following commands inside the CentOS guest to install the ACPI " -"service and configure it to start when the system boots:" -msgstr "" -"Lancez les commandes suivantes à l'intérieur de l'invité CentOS pour " -"installer le service ACPI et configurez-le pour démarrer lorsque le système " -"boot:" - -msgid "Run the installer:" -msgstr "Lancez l'installeur:" - -msgid "SSH server running" -msgstr "Serveur SSH en fonctionnement" - -msgid "SUSE Studio" -msgstr "SUSE Studio" - -msgid "" -"Second partition: A freebsd-ufs partition with a mount " -"point of / with all remaining free space." -msgstr "" -"Seconde partition: une partition freebsd-ufs avec le " -"point de montage / configurée avec tout l'espace libre " -"restant." - -msgid "" -"Select \"Yes\" when asked about installing the GRUB boot loader to the " -"master boot record." -msgstr "" -"Sélectionnez \"Oui\" lorsque vous serez interrogé à propos de l'installation " -"du chargeur de démarrage GRUB dans le master boot record (MBR)." - -msgid "" -"Select Create to create a partition table. This " -"action is the default when no partition table exists. Then, select " -"GPT GUID Partition Table from the list. This choice is " -"the default." -msgstr "" -"Sélectionnez Create pour créer une table de " -"partitions. Cette action est l'action par défaut quand aucune table de " -"partition n'existe. Puis, sélectionnez GPT GUID Partition Table dans la liste. C'est le choix par défaut." - -msgid "" -"Select Finish and then Commit " -"to commit your changes." -msgstr "" -"Sélectionnez Finish puis Commit pour confirmer vos changements." - -msgid "Select a mirror" -msgstr "Sélection d'un miroir" - -msgid "Select a root password." -msgstr "Sélectionnez un mot de passe root." - -msgid "Select the CMOS time zone." -msgstr "Sélectionnez la time zone CMOS." - -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 "" -"Sélectionnez les réglages par défaut pour toutes les autres options. Lorsque " -"l'installation est terminée, il vous sera demandé d'enlever le CD-ROM." - -msgid "Select the time zone appropriate to your environment." -msgstr "Sélectionnez la time zone appropriée à votre environnement." - -msgid "Serial port for logging: COM1" -msgstr "Port série pour la connexion : COM1 " - -msgid "Set the disk format for your image to one of the following values:" -msgstr "" -"Réglez le format disque pour votre image sur une des valeurs suivantes:" - -msgid "Set up disk partitioning." -msgstr "Partitionnement du disque." - -msgid "Set up the console:" -msgstr "Configurez la console:" - -msgid "Shut down the instance" -msgstr "Arrêter l'instance" - -msgid "Software selection: OpenSSH server" -msgstr "Sélection logicielle: serveur OpenSSH" - -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 "" -"Quelques clients VNC remplacent : (deux points) par ; (point-virgule) et _ " -"(underscore) par - (tiret). Si vous éditez un fichier par l'intermédiaire " -"d'une session VNC, soyez sûr que c'est http: et pas http; puis " -"authorized_keys et pas authorized-keys." - -msgid "" -"Some VNC clients replace the colon (:) with a semicolon " -"(;) and the underscore (_) with a " -"hyphen (-). Make sure to specify http: " -"and not http;. Make sure to specify " -"authorized_keys and not authorized-keys." -msgstr "" -"Quelques clients VNC remplacent les deux points (:) par " -"un point virgule (;) et l'underscore (_) avec un tiret (-). Soyez sûr de spécifier " -"http: et pas http;. Soyez sûr de " -"spécifier authorized_keys et pas authorized-" -"keys." - -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 "" -"Quelques fois, vous devrez modifier une image de machine virtuelle pour y " -"enlever toute trace de l'adresse MAC qui était attribuée à la carte de " -"l''interface réseau virtuelle lors de la création originale de l'image, car " -"l'adresse MAC sera différente lorsque qu'elle bootera la prochaine fois. Cet " -"exemple montre comment utiliser guestfish pour supprimer les références à la " -"vieille adresse MAC en supprimant le fichier /etc/udev/rules.d/70-" -"persistent-net.rules et en enlevant la ligne HWADDR du fichier /etc/sysconfig/network-scripts/ifcfg-eth0." - -msgid "" -"Start the Windows Server 2012 installation with the command:" -msgstr "" -"Démarrer l'installation de Windows Serveur 2012 avec la commande " -" :" - -msgid "Start the install process" -msgstr "Commencer le processus d'installation" - -msgid "Start the installation process" -msgstr "Lancez le processus d'installation" - -msgid "" -"Start the installation process by using either or " -" as described in the previous section. If you use " -", do not forget to connect your VNC client to the virtual " -"machine." -msgstr "" -"Commencez le processus d'installation en utilisant soit ou " -" comme décrit dans la section précédente. Si vous utilisez " -", n'oubliez pas de connecter votre client VNC à la machine " -"virtuelle." - -msgid "" -"Start the installation process using either or " -" as described in the previous section. If you use " -", do not forget to connect your VNC client to the virtual " -"machine." -msgstr "" -"Commencez le processus d'installation en utilisant soit ou " -" comme décrit dans la section précédente. Si vous utilisez " -", n'oubliez pas de connecter votre client VNC à la machine " -"virtuelle." - -msgid "Step through the install" -msgstr "Accomplir les étapes d'installation" - -msgid "" -"Step through the install, using the default options. When prompted for a " -"user name, the default (ubuntu) " -"is fine." -msgstr "" -"Effectuez les étapes d'installation, en utilisant les options par défaut. " -"Lorsqu'un nom d'utilisateur sera demandé, le nom par défaut (ubuntu) est correct." - -msgid "Step through the installation" -msgstr "Suivez les étapes d'installation" - -msgid "" -"Step through the installation, using the default options. The simplest thing " -"to do is to choose the \"Basic Server\" install (may be called \"Server\" " -"install on older versions of CentOS), which installs an SSH server." -msgstr "" -"Suivez les étapes d'installation, en utilisant les options par défaut. La " -"chose la plus simple à faire est de choisir l'installation \"Serveur de base" -"\" (qui peut aussi être appelée installation \"Serveur\" sur les versions de " -"CentOS plus anciennes), ce qui installe un serveur SSH." - -msgid "Storage devices" -msgstr "Périphériques de stockage" - -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 "" -"Le format d'image \"raw\" est le plus simple, et il est nativement supporté " -"à la fois par les hyperviseurs KVM et Xen. Vous pouvez vous représenter une " -"image raw comme étant l'équivalent binaire d'un fichier de périphérique de " -"bloc, créé comme si quelqu'un avait copié, disons, /dev/sda vers un fichier en utilisant la commande ." -"" - -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 "" -"Le drapeau -X passé à ssh va activer le transfert X11 au " -"travers d'ssh. Si cela ne fonctionne pas, essayez de le remplacer par le " -"drapeau -Y." - -msgid "" -"The -d3 flag tells Oz to show status information as it " -"runs." -msgstr "" -"Le drapeau -d3 indique à Oz de montrer les informations " -"de status comme il fonctionne." - -msgid "" -"The -u tells Oz to do the customization (install extra " -"packages, run the commands) once it does the initial install." -msgstr "" -"Le drapeau -u indique à Oz de réaliser la " -"personnalisation (installation de packages supplémentaires, lancement de " -"commandes) une fois qu'il a fait l'installation initiale." - -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 "" -"Le drapeau -x <filename> indique à Oz quel nom de " -"fichier utiliser pour écrire un fichier XML libvirt (autrement le fichier " -"par défaut serait sous la forme centos64Apr_03_2013-12:39:42)." - -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 "" -"Le package cloud-init prend automatiquement la clé " -"publique depuis le serveur de métadonnées et place la clé dans un compte. Le " -"compte varie par distribution. Sur des machines virtuelles basées sur " -"Ubuntu, le compte est dénommé ubuntu. Sur des machines " -"virtuelles basées sur fedora, le compte est dénommé ec2-user." - -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 "" -"Le script démarre lors du boot de l'instance et va chercher " -"un fournisseur de métadonnées à partir duquel prendre une clé publique. La " -"clé publique sera placée dans le compte utilisateur par défaut pour l'image." - -msgid "" -"The cloud-init package " -"automatically fetches the public key from the metadata server and places the " -"key in an account. You can install cloud-init inside the CentOS guest by adding the EPEL repo:" -msgstr "" -"Le package cloud-init prend " -"automatiquement la clé publique depuis le serveur de métadonnées et place la " -"clé dans un compte. Vous pouvez installer cloud-init à l'intérieur de l'invité CentOS en ajoutant le " -"dépôt EPEL:" - -msgid "" -"The KVM hypervisor starts the virtual machine with the libvirt name, " -"centos-6.4, with 1024MB 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 10GB 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 "" -"L'hyperviseur KVM démarre la machine virtuelle avec le nom libvirt, " -"centos-6.4, avec 1024 Mo de RAM. La machine virtuelle " -"possède aussi un lecteur de CD-ROM virtuel associé avec le fichier /data/" -"CentOS-6.4-x86_64-netinstall.iso et un disque dur local de 10 Go au format " -"qcow2 qui est stocké dans l'hôte sur /data/centos-6.4.qcow2. Le réseau est " -"configuré pour utiliser le réseau par défaut de libvirt. Il y a un serveur " -"VNC qui écoute sur toutes les interfaces, et libvirt ne tentera pas de " -"lancer un client VNC automatiquement ni ne tentera d'afficher la console " -"texte (--no-autoconsole). Finalement, libvirt tentera d'optimiser la " -"configuration pour un invité Linux faisant tourner une distribution RHEL 6.x." - -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 "" -"L'installeur Ubuntu vous demandera comment vous souhaitez gérer les mises à " -"jour sur votre système. Cette option dépend de votre cas spécifique " -"d'utilisation. Si vos instances de machines virtuelles seront reliées à " -"Internet, nous recommandons l'option \"Installer les mises à jour de " -"sécurité automatiquement\"." - -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 "" -"Le compte varie par distribution. Sur des machines virtuelles basées sur " -"Ubuntu, le compte est dénommé \"ubuntu\". Sur des machines virtuelles basées " -"sur Fedora, le compte est dénommé \"ec2-user\"." - -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 "" -"Le compte varie par distribution. Sur les machines virtuelles basées sur " -"Ubuntu, le compte est dénommé ubuntu. Sur les machines " -"virtuelles basées sur Fedora, le compte est dénommé ec2-user." - -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 "" -"Le format de conteneur indique si oui ou non l'image de machine virtuelle " -"est dans un format de fichier qui contient aussi les métadonnées de la " -"machine virtuelle courante." - -msgid "" -"The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 " -"support is enabled with DHCP, which is the default." -msgstr "" -"Les réglages TCP/IP par défaut conviennent. En particulier, assurez vous que " -"le support d'IPv4 soit actif avec DHCP, qui est le choix par défaut." - -msgid "The default mirror proposed by the installer should be fine." -msgstr "Le miroir par défaut proposé par l'installeur devrait convenir." - -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 "" -"Le format de disque d'une image de machine virtuelle est le format de " -"l'image disque sous-jacente. Les vendeurs d'appliances virtuelles possèdent " -"différents formats pour organiser les données contenues dans une image " -"disque de machine virtuelle." - -msgid "" -"The disk is not detected by default by the Windows installer. When requested " -"to choose an installation target, click Load driver " -"and browse the file system to select the E:\\WIN8\\AMD64 folder. The Windows installer displays a list of drivers to " -"install. Select the VirtIO SCSI and network drivers, and continue the " -"installation." -msgstr "" -"Le disque n'est pas détecté par défaut par l'installateur Windows. Quand on " -"demande de choisir une cible d'installation, cliquer Load driver naviguer dans le système de fichier pour sélectionner le dossier " -"E:\\WIN8\\AMD64. L'installateur Windows affiche une " -"liste de pilote à installer. Sélectionner le SCSI VirtIO et les pilotes " -"réseau et continuer l'installation. " - -msgid "The disk on the image has only one partition." -msgstr "Le disque sur l'image possède seulement une partition." - -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 "" -"La manière la plus simple de supporter ce type de fonctionnalité est " -"d'installer le package cloud-init à l'intérieur de votre " -"image, qui est configuré par défaut pour traiter les données utilisateur en " -"tant que script exécutable, et configurer le nom d'hôte." - -msgid "The file system on the one partition is ext3 or ext4." -msgstr "Le système de fichiers sur cette partition est ext3 ou ext4." - -msgid "" -"The following figure shows a completed partition table with a 1GB virtual " -"disk:" -msgstr "" -"La figure suivante montre une table de partitions complétée avec un disque " -"virtuel de 1 Go:" - -msgid "" -"The installer may ask you to choose a host name. The default " -"(localhost.localdomain) is fine. You install the " -"cloud-init package later, which " -"sets the host name on boot when a new instance is provisioned using this " -"image." -msgstr "" -"L'installeur pourrait vous demander de choisir un nom d'hôte. Le nom par " -"défaut (localhost.localdomain) est bon. Vous installez le " -"package cloud-init plus tard, qui " -"configure le nom d'hôte au boot lorsqu'une nouvelle instance est " -"provisionnée en utilisant cette image." - -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 "" -"L'installeur peut vous demander de choisir un nom d'hôte. Le nom par défaut " -"(ubuntu) convient. Nous installerons le package cloud-" -"init plus tard, qui configurera le nom d'hôte au boot lorsqu'une nouvelle " -"instance utilisant cette image est provisionnée." - -msgid "" -"The minimum supported disk size for FreeBSD is 1GB. Because the goal is to " -"make the smallest possible base image, the example uses that minimum size. " -"This size is sufficient to include the optional doc, games, and lib32 " -"collections. To include the ports collection, add another 1GB. To include " -"src, add 512MB." -msgstr "" -"La taille de disque minimale supportée pour FreeBSD est de 1 Go. Puisque le " -"but est d'obtenir la taille la plus petite possible pour l'image de base, " -"l'exemple utilise cette taille minimale. Cette taille est suffisante pour " -"inclure la documentation optionnelle, les jeux, et les collections lib32. " -"Pour inclure la collection de ports, ajoutez 1 Go supplémentaire. Pour " -"inclure src, ajoutez 512 Mo." - -msgid "" -"The name of your virtual machine image is centos-6.4; you " -"need this name when you use commands to manipulate the " -"state of the image." -msgstr "" -"Le nom de l'image de votre machine virtuelle est centos-6.4; vous avez besoin de ce nom lorsque vous utilisez les commandes " -" pour manipuler l'état de l'image." - -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 "" -"Le système d'exploitation enregistre l'adresse MAC de la carte virtuelle " -"Ethernet installée dans /etc/sysconfig/network-scripts/ifcfg-eth0 et /etc/udev/rules.d/70-persistent-net.rules " -"pendant le processus de l'instance. Cependant, à chaque démarrage de " -"l'image, la carte virtuelle Ethernet aura une adresse MAC différente alors " -"cette information devra être supprimée du fichier de configuration. " - -msgid "" -"The previous script only gets the ssh public key from the metadata server. " -"It does not get user data, which is optional data that can be passed by the " -"user when requesting a new instance. User data is often used to run a custom " -"script when an instance boots." -msgstr "" -"Le script précédent obtient la clé publique ssh seulement à partir du " -"serveur de métadonnées. Il n'obtient pas les données utilisateur, qui sont " -"des données optionnelles qui peuvent être transmises par l'utilisateur " -"lorsqu'une nouvelle instance est demandée. Les données utilisateur sont " -"souvent utilisées pour lancer un script personnalisé lorsqu'une instance " -"démarre." - -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 5GB 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 10GB. When the disk for an instance is resized up, " -"zeros are just added to the end." -msgstr "" -"La taille d'un disque dans une image de machine virtuelle est déterminées " -"lorsque vous créez l'image initialement. Cependant, OpenStack vous laisse la " -"liberté de lancer les instances avec des lecteurs de tailles différentes en " -"indiquant différentes branches. Par exemple, si votre image a été créée avec " -"un disque de 5 Go, et que vous lancez une instance avec la branche m1.small. " -"L'instance de machine virtuelle résultante a, par défaut, un disque primaire " -"d'une taille de 10 Go. Lorsque le disque d'une instance est agrandit, des " -"zéros sont juste ajoutés à la fin." - -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 "" -"La méthode typique utilisée par les utilisateurs pour accéder les machines " -"virtuelles fonctionnant sous OpenStack est d'utiliser ssh avec " -"l'authentification par clé publique. Pour que ceci fonctionne, votre image " -"de machine virtuelle doit être configurée pour télécharger la clé publique " -"ssh à partir du service de métadonnées d'OpenStack ou du lecteur de " -"configuration, lors du démarrage." - -msgid "" -"The virtualized CMOS almost always stores its time in UTC, so unless you " -"know otherwise, select UTC." -msgstr "" -"Le CMOS virtualisé stocke pratiquement toujours son heure au format UTC, " -"donc à moins que vous ne connaissiez votre timezone, sélectionnez UTC." - -msgid "Then, during the boot process, you must:" -msgstr "Ensuite, durant le processus de démarrage, vous devez:" - -msgid "" -"There are different options for partitioning the disks. The default " -"installation uses LVM partitions, and creates three partitions (/" -"boot, /, swap), which works fine. " -"Alternatively, you might want to create a single ext4 partition that is " -"mounted to \"/\", which also works fine." -msgstr "" -"Il y a différentes options possibles pour partitionner les disques. " -"L'installation par défaut utilise des partitions LVM, et crée trois " -"partitions (/boot, /, swap), ce " -"qui convient bien. Alternativement, vous pourriez vouloir créer une " -"partition ext4 unique montée sur \"/\", ce qui " -"conviendrait aussi." - -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 "" -"Il y a différentes options pour partitionner les disques. L'installation par " -"défaut utilise des partitions LVM, et va créer trois partitions (/" -"boot, /, swap), et cela conviendra " -"parfaitement. Alternativement, vous pouvez choisir de créer une unique " -"partition ext4, montée sur \"/\", et cela devrait " -"convenir aussi." - -msgid "There are several tools that are designed to automate image creation." -msgstr "" -"Il y a plusieurs outils qui sont conçus pour automatiser la création " -"d'images.\n" -"\n" -"Pour construire une image, utiliser le scripte suivant:" - -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 "" -"Il y a un utilitaire appelé , qui réalise différentes tâches " -"de nettoyage comme enlever les références à l'adresse MAC. Il va nettoyer " -"une image de machine virtuelle sur place:" - -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 "" -"C'est pourquoi, si vous utilisez Xen, nous recommandons lors de la création " -"de vos images, de créer une unique partition ext3 ou ext4 (non gérée par " -"LVM). Dans le cas contraire, continuez à lire." - -msgid "This VM must also have Internet access to download packages." -msgstr "" -"Cette VM doit aussi disposer d'un accès Internet afin de télécharger les " -"packages." - -msgid "" -"This example creates a Windows Server 2012 qcow2 image, using and the KVM hypervisor." -msgstr "" -"Cet exemple crée une image qcow2 Windows Server 2012, en utilisant " -" et l'hyperviseur KVM." - -msgid "" -"This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image " -"for a different version of Ubuntu, follow these steps with the noted " -"differences." -msgstr "" -"Cet exemple installe une image Ubuntu 14.04 (Trusty Tahr). Pour créer une " -"image pour une version différente d'ubuntu, suivez ces étapes en prenant " -"garde aux différences portées à votre attention." - -msgid "" -"This example shows how to create a FreeBSD 10 image. To create a FreeBSD 9.2 " -"image, follow these steps with the noted differences." -msgstr "" -"Cet exemple montre comment créer une image FreeBSD 10. Pour créer une image " -"FreeBSD 9.2, suivez ces étapes en notant bien les différences." - -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 "" -"Cet exemple montre comment utiliser pour modifier un " -"fichier. La commande peut prendre soit un nom de fichier en argument avec le " -"drapeau -a, soit un nom de domaine en argument avec le " -"drapeau -d. Les exemples suivants montrent comment " -"utiliser ça pour modifier le fichier /etc/shadow dans " -"l'instance avec le nom de domaine libvirt instance-000000e1 qui est actuellement en fonctionnement:" - -msgid "" -"This example shows you how to install a CentOS image and focuses mainly on " -"CentOS 6.4. Because the CentOS installation process might differ across " -"versions, the installation steps might differ if you use a different version " -"of CentOS." -msgstr "" -"Cet exemple vous montre comment installer une image CentOS et se concentre " -"principalement sur CentOS 6.4. Puisque le processus d'installation pourrait " -"différer entre les versions, les étapes d'installation pourraient différer " -"si vous utilisez une version différente de CentOS." - -msgid "" -"This guide describes how to obtain, create, and modify virtual machine " -"images that are compatible with OpenStack." -msgstr "" -"Ce guide décrit comment obtenir, créer, et modifier des images de machine " -"virtuelle qui sont compatibles avec OpenStack." - -msgid "This is a virtual machine image in raw format, as described above." -msgstr "" -"C'est une image de machine virtuelle au format raw, comme décrit au-dessus." - -msgid "" -"This menu enables you to update previous settings. Check that the settings " -"are correct, and click exit." -msgstr "" -"Ce menu vous permet de modifier des réglages précédents. Vérifiez que les " -"réglages sont corrects, et cliquez sur exit." - -msgid "" -"This sets console output to go to the serial console, which is displayed by " -", and the video console for sites with VNC or Spice " -"configured." -msgstr "" -"Cela configure la sortie de la console pour aller sur la console série, qui " -"est affichée par , et la console vidéo pour les sites " -"configurés avec VNC ou Spice." - -msgid "" -"This starts a guestfish session. Note that the guestfish prompt looks like a " -"fish: > <fs>." -msgstr "" -"Cela lance une session guestfish. Notez que le prompt guestfish ressemble à " -"un poisson: > <fs>." - -msgid "" -"To allow Cloudbase-Init to run scripts during an " -"instance boot, set the PowerShell execution policy to be unrestricted:" -msgstr "" -"Pour autoriser Cloudbase-Init à lancer des scripts " -"durant le démarrage d'une instance, positionner la priorité d'exécution de " -"PowerShell à illimitée :" - -msgid "To build an image, call the following script:" -msgstr "Cet exemple fait creer une image Ubuntu speciale du ernier lance." - -msgid "To create a FreeBSD image" -msgstr "Pour créer une image FreeBSD" - -msgid "" -"To eject a disk by using the command, libvirt requires that " -"you attach an empty disk at the same target that the CDROM was previously " -"attached, which should be hdc. You can confirm the " -"appropriate target using the command." -msgstr "" -"Pour éjecter un disque en utilisant la commande , libvirt a " -"besoin que vous attachiez un disque vide à la même cible à laquelle le CD-" -"ROM était précédemment attaché, qui devrait être hdc. " -"Vous pouvez confirmer la cible appropriée en utilisant la commande " -"." - -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 "" -"Pour éjecter un disque en utilisant , libvirt a besoin que " -"vous attachiez un disque vide sur la même cible à laquelle le CDROM était " -"attaché auparavant, et qui devrait être hdc. Vous pouvez " -"confirmer la cible appropriée en utilisant la commande ." - -msgid "" -"To enable the hypervisor to reboot or shutdown an instance, you must install " -"and run the acpid service on the " -"guest system." -msgstr "" -"Afin de permettre à l'hyperviseur de rebooter ou éteindre une instance, vous " -"devez installer et lancer le service acpid sur le système invité." - -msgid "" -"To install the operating system, complete the following steps inside the VM:" -msgstr "" -"Pour installer le système d'exploitation, complétez les étapes suivantes à " -"l'intérieur de la VM:" - -msgid "" -"To keep things brief, we'll sometimes use the term \"image\" instead of " -"\"virtual machine image\"." -msgstr "" -"Pour conservé une certaine brièveté des choses, nous utiliserons de temps en " -"temps le terme \"image\" au lieu d'\"image de machine virtuelle\"." - -msgid "" -"To see how the settings affect the deletion of a running instance, check the " -"directory where the images are stored:" -msgstr "" -"Pour voir comment les réglages affectent la suppression d'une instance en " -"cours de fonctionnement, vérifiez le dossier où les images sont stockées:" - -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 "" -"Pour configurer la source de métadonnées que l'image doit utiliser lancez la " -"commande contre le package cloud-init. " -"Lorsque cela vous sera demandé, sélectionnez la source de données " -"EC2:" - -msgid "" -"To verify that the libvirt \"default\" network is enabled, use the " -" command and verify that the \"default\" network is active:" -msgstr "" -"Pour vérifier que le réseau \"défaut\" de libvirt soit activé, utilisez la " -"commande et vérifiez que le réseau \"défaut\" soit actif:" - -msgid "Tool support for image creation" -msgstr "Support de l'outil pour la création d'image" - -msgid "UEC tarball" -msgstr "tarball UEC" - -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 "" -"Le Cloud Entreprise Ubuntu renvoi à une solution de cloud Ubuntu obsolète " -"basée sur Eucalyptus qui a été remplacée par l'Infrastructure de Cloud " -"Ubuntu basée sur OpenStack." - -msgid "Undefine the libvirt domain" -msgstr "Suppression de la définition du domaine libvirt" - -msgid "Use cloud-init to fetch the public key" -msgstr "Utilisez cloud-init pour prendre la clé publique" - -msgid "" -"Use or to connect to the VM and start the " -"Windows installation." -msgstr "" -"Utiliser ou pour se connecter à la VM et " -"démarrer l'installation Windows." - -msgid "Use cloud-init to fetch the public key" -msgstr "Utilisez cloud-init pour prendre la clé publique." - -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 "" -"Utilisez les options dans nova.conf pour contrôler si, " -"et pour combien de temps, les images de base inutilisées sont stockées dans " -"/var/lib/nova/instances/_base/. Si vous avez configuré " -"la migration à chaud des instances, tous vos noeuds de calcul partagent un " -"dossier /var/lib/nova/instances/ commun." - -msgid "Use the command to get the VNC port number." -msgstr "" -"Utilisez la commande pour obtenir le numéro de port VNC." - -msgid "Use the virt-manager X11 GUI" -msgstr "Utilisation de l'interface graphique X11 virt-manager" - -msgid "Use virt-install and connect by using a local VNC client" -msgstr "" -"Utilisation de virt-install et connexion en utilisant un client local VNC" - -msgid "Username: Administrator" -msgstr "Utilisateur : Administrator" - -msgid "VBoxManage: VDI (VirtualBox) to raw" -msgstr "VBoxManage: VDI (VirtualBox) à raw" - -msgid "VDI" -msgstr "VDI" - -msgid "VDI (VirtualBox)" -msgstr "VDI (VirtualBox)" - -msgid "VHD" -msgstr "VHD" - -msgid "VHD (Hyper-V)" -msgstr "VHD (Hyper-V)" - -msgid "VHDX" -msgstr "VHDX" - -msgid "VM Image Guide" -msgstr "Guide d'Image de VM" - -msgid "VMBuilder" -msgstr "VMBuilder" - -msgid "VMDK" -msgstr "VMDK" - -msgid "VMDK (VMware)" -msgstr "VMDK (VMware)" - -msgid "VeeWee" -msgstr "VeeWee" - -msgid "Verify the libvirt default network is running" -msgstr "Vérifier que le réseau par défaut libvirt est en fonctionnement" - -msgid "Wait for the machine shutdown." -msgstr "Attendre l'arrêt de la machine." - -msgid "" -"We don't recommend creating raw images by dd'ing block device files, we " -"discuss how to create raw images later." -msgstr "" -"Nous ne recommandons pas la création d'images raw en utilisant la commande " -"dd sur des fichiers de périphérique bloc, nous discutons de la façon dont on " -"peut créer des images raw plus loin." - -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 "" -"Pour commencer nous devons utiliser la commande au prompt " -"guestfish avant de pouvoir faire quoique ce soit d'autre. Une machine " -"virtuelle sera lancée, qui sera utilisée pour réaliser toutes les " -"manipulations de fichier. Nous pouvons maintenant visualiser " -"les systèmes de fichiers de l'image en utilisant la commande :Nous avons besoin de monter le volume logique qui contient " -"la partition root: " - -msgid "" -"We're done, so we can exit using the command:" -msgstr "" -"Ceci étant fait, nous pouvons quitter en utilisant la commande " -": " - -msgid "Web site name: mirror.umd.edu" -msgstr "Nom de site web: mirror.umd.edu" - -msgid "What is a virtual machine image?" -msgstr "Qu'est ce qu'une image de machine virtuelle?" - -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 "" -"Lorsque des images Ubuntu sont construites doit être " -"explicitement configuré pour la source de métadonnées utilisée. Le serveur " -"de métadonnées OpenStack émule le service de métadonnées EC2 utilisé par les " -"images dans Amazon EC2." - -msgid "" -"When prompted about the optional doc, games, lib32, ports, and " -"src system components, select only those that you need. " -"It is possible to have a fully functional installation without selecting " -"additional components selected. As noted previously, a minimal system with a " -"1GB virtual disk supports doc, games, and lib32 inclusive. The ports " -"collection requires at least 1GB additional space and possibly more if you " -"plan to install many ports. The src collection requires an additional 512MB." -msgstr "" -"Lorsque vous serez consulté à propos des composants système optionnels " -"doc, games, lib32, " -"ports, et src, sélectionnez seulement " -"ceux qui vous sont nécessaires. Il est aussi possible d'avoir une " -"installation pleinement fonctionnelle sans prendre les composants " -"sélectionnés additionnels. Comme noté précédemment, un système minimal avec " -"un disque virtuel de 1 Go supporte la documentation, les jeux, et lib32. La " -"collection de ports demande au moins 1 Go d'espace supplémentaire et peut " -"être plus si vous prévoyez d'installer plusieurs ports. La collection src " -"demande 512 Mo de plus." - -msgid "" -"When prompted, choose to run the ISO in Install mode." -msgstr "" -"Lorsque cela vous est demandé, choisissez de lancez l'ISO en mode " -"Installation." - -msgid "" -"When the installation is done, in the Complete the Cloudbase-Init " -"Setup Wizard window, select the Run Sysprep " -"and Shutdown check boxes and click Finish." -msgstr "" -"Quand l'installation est effectuée, dans la fenêtre Complete the " -"Cloudbase-Init Setup Wizard, sélectionner les cases Run " -"Sysprep et Shutdown et cliquer sur " -"Finish." - -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 "" -"Lorsque vous utilisez des images au format qcow2 vous devriez vérifier " -"l'option 'personnaliser avant l'installation', aller dans les propriétés du " -"disque et explicitement sélectionner le format qcow2. Cela donne la garantie " -"que la taille du disque de la machine virtuelle sera correcte." - -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 "" -"Lorsque le réseau default de libvirt est utilisé, libvirt " -"va connecter l'interface de la machine virtuelle à un pont appelé " -"virbr0. Il y a un process dnsmasq géré par libvirt qui v " -"délivrer une adresse IP sur le sous-réseau 192.168.122.0/24, et libvirt " -"possède des règles iptables pour réaliser du NAT pour les adresses IP de ce " -"sous-réseau." - -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 "" -"Lorsque vous bootez pour la première fois après l'installation, des outils " -"d'authentification peuvent vous demander certaines configurations, mais vous " -"pouvez juste choisir 'Sortir'. Ensuite, loguez-vous en tant que root en " -"utilisant le mot de passe root que vous avez spécifié." - -msgid "" -"When you boot for the first time after installation, you might be prompted " -"about authentication tools. Select Exit. Then, log in " -"as root." -msgstr "" -"Lorsque vous bootez pour la première fois après l'installation, il pourrait " -"vous être demandé d'effectuer des réglages à propos des outils " -"d'authentification. Sélectionnez Exit. Puis, loguez-" -"vous en tant que root." - -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 "" -"Lorsque vous créez une image Linux, vous devez décider comment partitionner " -"les disques. Le choix d'une méthode de partitionnement peut affecter la " -"fonctionnalité de redimensionnement, comme décrit dans les sections " -"suivantes." - -msgid "When you're done, clean up:" -msgstr "Une fois ceci terminé, nettoyez:" - -msgid "When you're done, clean up:" -msgstr "Une fois ceci fait, nettoyez:" - -msgid "Write a custom script to fetch the public key" -msgstr "Ecrire un script personnalisé pour prendre la clé publique" - -msgid "Write a script to fetch the public key (if no cloud-init)" -msgstr "Ecrire un script pour prendre la clé publique (si pas de cloud-init)" - -msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" -msgstr "Xen: 1 partition ext3/ext4 (pas de LVM, pas de /boot, pas de swap)" - -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 "" -"Vous pouvez modifier le nom du compte utilisé par cloud-init en éditant le fichier /etc/cloud/cloud.cfg " -"pour y ajouter une ligne avec un utilisateur différent. Par exemple, pour " -"configurer cloud-init pour mettre la clé dans un compte " -"dénommé admin, éditez le fichier de configuration afin " -"qu'il comprenne la ligne:" - -msgid "" -"You can change the name of the account used by cloud-init by editing the /etc/cloud/cloud.cfg file and adding a line with a different user. For example, to " -"configure cloud-init to put the " -"key in an account named admin, add this line to the " -"configuration file:" -msgstr "" -"Vous pouvez modifier le nom du compte utilisé par cloud-init en éditant le fichier /etc/cloud/cloud." -"cfg et en y ajoutant une ligne avec un utilisateur différent. Par " -"exemple, pour configurer cloud-init pour mettre la clé dans un compte dénommé admin, ajoutez cette ligne au fichier de configuration:" - -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 "" -"Vous pouvez modifier le nom du compte utilisé par cloud-init en éditant le " -"fichier /etc/cloud/cloud.cfg pour y ajouter une ligne " -"avec un utilisateur différent. Par exemple, pour configurer cloud-init afin " -"qu'il mette la clé dans un compte dénommé \"admin\", éditez le fichier de " -"configuration afin qu'il comporte la ligne:" - -msgid "" -"You can set the container format for your image to one of the following " -"values:" -msgstr "" -"Vous pouvez régler le format de conteneur pour votre image sur l'une des " -"valeurs suivantes:" - -msgid "" -"You can specify up to 1GB additional RAM to make the installation process " -"run faster." -msgstr "" -"Vous pouvez configurer jusqu'à 1 Go de RAM supplémentaire pour faire en " -"sorte que le processus d'installation se déroule plus rapidement." - -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 "" -"Vous n'avez pas besoin d'une partition /boot à moins " -"que votre image est une vieille distribution Linux qui nécessite que " -"/boot ne soit pas géré par LVM." - -msgid "" -"You do not need to add users at this time. The bsd-cloudinit program adds a freebsd user account if one " -"does not exist. The ssh keys for " -"this user are associated with OpenStack. To customize this user account, you " -"can create it now. For example, you might want to customize the shell for " -"the user." -msgstr "" -"Il n'est pas nécessaire d'ajouter des utilisateurs à ce moment. Le programme " -"bsd-cloudinit ajoute un compte d'utilisateur " -"freebsd si aucun n'existe. Les clés ssh de cet utilisateur sont associées avec " -"OpenStack. Pour personnaliser ce compte utilisateur, vous pouvez le créer " -"maintenant. Par exemple, vous pourriez personnaliser le shell de cet " -"utilisateur." - -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 "" -"Vous devez configurer l'image de telle façon que le kernel écrive le journal " -"de démarrage sur le périphérique ttyS0. En particulier, " -"l'argument console=ttyS0 doit être passé au kernel lors " -"du démarrage." - -msgid "You must configure these items for your image:" -msgstr "Vous devez configurer ces éléments pour votre image:" - -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 "" -"Vous devez installer un serveur ssh à l'intérieur de l'image pour être " -"certain qu'il soit lancé au démarrage, ou vous ne pourrez pas vous connecter " -"à votre instance en utilisant ssh lorsqu'elle démarrera à l'intérieur " -"d'OpenStack. Ce package est typiquement appelé openssh-server." - -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 "" -"Vous avez besoin du module kernel nbd (network block " -"device) chargé pour monter des images qcow2. Il sera chargé avec le support " -"des périphériques 16 blocs, ce qui est parfait pour nos besoins. En tant que " -"root:" - -msgid "" -"You now have a VM that boots from the downloaded install ISO and is " -"connected to the blank virtual disk that you created previously." -msgstr "" -"Vous disposez maintenant d'une VM qui boot depuis l'ISO d'installation " -"téléchargée et qui est connectée au disque virtuel vierge que vous avez créé " -"précédemment." - -msgid "" -"You saved the netinstall ISO image to the /data/isos " -"directory." -msgstr "" -"Vous avez sauvegardé l'image ISO netinstall dans le dossier /data/" -"isos." - -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 "" -"Votre image doit être capable de redimensionner ses partitions au boot pour " -"correspondre à la taille requise par l'utilisateur. Autrement, une fois que " -"l'instance démarre, vous devez redimensionner manuellement les partitions " -"pour accéder à l'espace de stockage supplémentaire auquel vous avez accès " -"lorsque la taille du disque associé avec la branche excède la taille disque " -"avec laquelle votre image a été créée." - -msgid "Your script must do something like the following:" -msgstr "" -"Votre script doit faire quelque chose comme ce qui suit:" - -msgid "current" -msgstr "en cours" - -msgid "guestfish" -msgstr "guestfish" - -msgid "guestmount" -msgstr "guestmount" - -msgid "imagefactory" -msgstr "imagefactory" - -msgid "img-uuid" -msgstr "img-uuid" - -msgid "node-root" -msgstr "noeud-racine" - -msgid "preallocate_images=none" -msgstr "preallocate_images=none" - -msgid "qcow2" -msgstr "qcow2" - -msgid "qemu-img format strings" -msgstr "Format des chaines qemu-img" - -msgid "raw" -msgstr "raw" - -msgid "remove_unused_base_images=True" -msgstr "remove_unused_base_images=True" - -msgid "remove_unused_original_minimum_age_seconds=86400" -msgstr "remove_unused_original_minimum_age_seconds=86400" - -msgid "remove_unused_resized_minimum_age_seconds=3600" -msgstr "remove_unused_resized_minimum_age_seconds=3600" - -msgid "sda6" -msgstr "sda6" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -msgid "translator-credits" -msgstr "" -"Olivier Buisson , 2012 | Cloudwatt Team , 2013" - -msgid "vdi" -msgstr "vdi" - -msgid "vg00" -msgstr "vg00" - -msgid "virt-* tools" -msgstr "virt-*tools" - -msgid "vm-image" -msgstr "vm-image" - -msgid "vm-name" -msgstr "vm-name" - -msgid "vmdk" -msgstr "vmdk" - -msgid "vpc" -msgstr "vpc" diff --git a/doc/image-guide/locale/image-guide.pot b/doc/image-guide/locale/image-guide.pot deleted file mode 100644 index e1b373f825..0000000000 --- a/doc/image-guide/locale/image-guide.pot +++ /dev/null @@ -1,2338 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-23 06:29+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:7(title) -msgid "Tool support for image creation" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:9(para) -msgid "There are several tools that are designed to automate image creation." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:12(title) -msgid "Diskimage-builder" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:13(para) -msgid "Diskimage-builder is an automated disk image creation tool that supports a variety of distributions and architectures. Diskimage-builder (DIB) can build images for Fedora, Red Hat Enterprise Linux, Ubuntu, Debian, CentOS, and openSUSE. DIB is organized in a series of elements that build on top of each other to create specific images." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:20(para) -msgid "To build an image, call the following script:" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:22(para) -msgid "This example creates a generic, bootable Ubuntu image of the latest release." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:24(para) -msgid "Further customization could be accomplished by setting environment variables or adding elements to the command-line:" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:27(para) -msgid "This example creates the image as before, but for arm architecture. More elements are available in the git source directory and documented in the diskimage-builder elements documentation." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:37(title) -msgid "Oz" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:38(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.xml:48(para) -msgid "As of this writing, there are no Oz packages for Ubuntu, so you will need to either install from the source or build your own .deb file." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:52(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.xml:58(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.xml:97(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.xml:105(para) -msgid "After Oz completes the initial OS install using the kickstart file, it customizes the image with an update. It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the command section of the XML file." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:110(para) -msgid "To run this:" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:114(para) -msgid "The -d3 flag tells Oz to show status information as it runs." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:118(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.xml:123(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.xml:129(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:" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:134(para) -msgid "Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh into the instance and perform the customizations." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:138(title) -msgid "VMBuilder" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:139(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.xml:146(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.xml:153(title) -msgid "VeeWee" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:154(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.xml:160(title) -msgid "Packer" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:161(para) -msgid " Packer is a tool for creating machine images for multiple platforms from a single source configuration." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:167(title) -msgid "imagefactory" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:168(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.xml:175(title) -msgid "SUSE Studio" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:176(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 "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_centos-example.xml:71(None) ./doc/image-guide/section_centos-example.xml:74(None) -msgid "@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_centos-example.xml:84(None) -msgid "@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_centos-example.xml:93(None) -msgid "@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_centos-example.xml:106(None) -msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_centos-example.xml:157(None) -msgid "@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:4(title) -msgid "Example: CentOS image" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:5(para) -msgid "This example shows you how to install a CentOS image and focuses mainly on CentOS 6.4. Because the CentOS installation process might differ across versions, the installation steps might differ if you use a different version of CentOS." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:9(title) -msgid "Download a CentOS install ISO" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:11(para) -msgid "Navigate to the CentOS mirrors page." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:16(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.xml:20(para) -msgid "Click the folder link of the CentOS version that you want to use. For example, 6.4/." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:24(para) -msgid "Click the isos/ folder link." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:27(para) -msgid "Click the x86_64/ folder link for 64-bit images." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:30(para) -msgid "Click the netinstall ISO image that you want to download. For example, CentOS-6.4-x86_64-netinstall.iso is a good choice because it is a smaller image that downloads missing packages from the Internet during installation." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:37(title) -msgid "Start the installation process" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:38(para) -msgid "Start the installation process using either or as described in the previous section. If you use , do not forget to connect your VNC client to the virtual machine." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:42(para) -msgid "Assume that:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:45(para) -msgid "The name of your virtual machine image is centos-6.4; you need this name when you use commands to manipulate the state of the image." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:50(para) -msgid "You saved the netinstall ISO image to the /data/isos directory." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:53(para) -msgid "If you use , the commands should look something like this:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:65(title) ./doc/image-guide/section_centos-example.xml:146(title) -msgid "Step through the installation" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:66(para) -msgid "At the initial Installer boot menu, choose the Install or upgrade an existing system option. Step through the installation prompts. Accept the defaults." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:79(title) -msgid "Configure TCP/IP" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:80(para) -msgid "The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 support is enabled with DHCP, which is the default." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:89(title) -msgid "Point the installer to a CentOS web server" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:90(para) -msgid "Choose URL as the installation method." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:96(para) -msgid "Depending on the version of CentOS, the net installer requires the user to specify either a URL or the web site and a CentOS directory that corresponds to one of the CentOS mirrors. If the installer asks for a single URL, a valid URL might be http://mirror.umd.edu/centos/6/os/x86_64." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:101(para) -msgid "Consider using other mirrors as an alternative to mirror.umd.edu." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:109(para) -msgid "If the installer asks for web site name and CentOS directory separately, you might enter:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:113(para) -msgid "Web site name: mirror.umd.edu" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:116(para) -msgid "CentOS directory: centos/6/os/x86_64" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:119(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.xml:124(title) -msgid "Storage devices" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:125(para) -msgid "If prompted about which type of devices your installation uses, choose Basic Storage Devices." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:129(title) ./doc/image-guide/section_ubuntu-example.xml:47(title) -msgid "Hostname" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:130(para) -msgid "The installer may ask you to choose a host name. The default (localhost.localdomain) is fine. You install the cloud-init package later, which sets the host name on boot when a new instance is provisioned using this image." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:136(title) ./doc/image-guide/section_ubuntu-example.xml:64(title) -msgid "Partition the disks" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:137(para) -msgid "There are different options for partitioning the disks. The default installation uses LVM partitions, and creates three partitions (/boot, /, swap), which works fine. Alternatively, you might want to create a single ext4 partition that is mounted to \"/\", which also works fine." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:142(para) -msgid "If unsure, use the default partition scheme for the installer because no scheme is better than another." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:147(para) -msgid "Step through the installation, using the default options. The simplest thing to do is to choose the \"Basic Server\" install (may be called \"Server\" install on older versions of CentOS), which installs an SSH server." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:152(title) ./doc/image-guide/section_ubuntu-example.xml:103(title) -msgid "Detach the CD-ROM and reboot" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:153(para) -msgid "When the installation has completed, the Congratulations, your CentOS installation is complete screen appears." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:163(replaceable) ./doc/image-guide/section_centos-example.xml:323(replaceable) ./doc/image-guide/section_ubuntu-example.xml:120(replaceable) ./doc/image-guide/section_ubuntu-example.xml:199(replaceable) -msgid "vm-image" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:160(para) -msgid "To eject a disk by using the command, libvirt requires that you attach an empty disk at the same target that the CDROM was previously attached, which should be hdc. You can confirm the appropriate target using the command." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:177(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.xml:185(title) ./doc/image-guide/section_ubuntu-example.xml:149(title) -msgid "Log in to newly created image" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:186(para) -msgid "When you boot for the first time after installation, you might be prompted about authentication tools. Select Exit. Then, log in as root." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:190(title) -msgid "Install the ACPI service" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:191(para) -msgid "To enable the hypervisor to reboot or shutdown an instance, you must install and run the acpid service on the guest system." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:195(para) -msgid "Run the following commands inside the CentOS guest to install the ACPI service and configure it to start when the system boots:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:202(title) -msgid "Configure to fetch metadata" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:203(para) -msgid "An instance must interact with the metadata service to perform several tasks on start up. For example, the instance must get the ssh public key and run the user data script. To ensure that the instance performs these tasks, use one of these methods:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:208(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.xml:213(para) -msgid "Modify /etc/rc.local to fetch desired information from the metadata service, as described in the next section." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:219(title) -msgid "Use cloud-init to fetch the public key" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:220(para) -msgid "The cloud-init package automatically fetches the public key from the metadata server and places the key in an account. You can install cloud-init inside the CentOS guest by adding the EPEL repo:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:226(para) -msgid "The account varies by distribution. On Ubuntu-based virtual machines, the account is called ubuntu. On Fedora-based virtual machines, the account is called ec2-user." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:229(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, add this line to the configuration file:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:237(title) -msgid "Write a script to fetch the public key (if no cloud-init)" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:238(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.d/rc.local file and add the following lines before the line touch /var/lock/subsys/local:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:267(para) -msgid "Some VNC clients replace the colon (:) with a semicolon (;) and the underscore (_) with a hyphen (-). Make sure to specify http: and not http;. Make sure to specify authorized_keys and not authorized-keys." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:275(para) -msgid "The previous script only gets the ssh public key from the metadata server. It does not get user data, which is optional data that can be passed by the user when requesting a new instance. User data is often used to run a custom script when an instance boots." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:279(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 get user data." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:286(title) -msgid "Disable the zeroconf route" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:287(para) -msgid "For the instance to access the metadata service, you must disable the default zeroconf route:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:292(title) -msgid "Configure console" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:293(para) -msgid "For the command to work properly on CentOS 6.x, you might need to add the following lines to the /boot/grub/menu.lst file:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:299(replaceable) -msgid "..." -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:302(title) ./doc/image-guide/section_ubuntu-example.xml:179(title) -msgid "Shut down the instance" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:303(para) ./doc/image-guide/section_ubuntu-example.xml:180(para) -msgid "From inside the instance, as root:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:307(title) ./doc/image-guide/section_ubuntu-example.xml:184(title) -msgid "Clean up (remove MAC address details)" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:308(para) ./doc/image-guide/section_fedora-example.xml:153(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.xml:314(para) ./doc/image-guide/section_ubuntu-example.xml:190(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.xml:320(title) ./doc/image-guide/section_ubuntu-example.xml:196(title) -msgid "Undefine the libvirt domain" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:321(para) -msgid "Now that you can upload the image to the Image service, you no longer need to have this virtual machine image managed by libvirt. Use the command to inform libvirt:" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:327(title) ./doc/image-guide/section_ubuntu-example.xml:203(title) -msgid "Image is complete" -msgstr "" - -#: ./doc/image-guide/section_centos-example.xml:328(para) -msgid "The underlying image file that you created with is ready to be uploaded. For example, you can upload the /tmp/centos-6.4.qcow2 image to the Image service." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:7(title) -msgid "Introduction" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:8(para) -msgid "An OpenStack Compute cloud is not very useful unless you have virtual machine images (which some people call \"virtual appliances\"). This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:11(para) -msgid "To keep things brief, we'll sometimes use the term \"image\" instead of \"virtual machine image\"." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:13(para) -msgid "What is a virtual machine image?" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:14(para) -msgid "A virtual machine image is a single file which contains a virtual disk that has a bootable operating system installed on it." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:16(para) -msgid "Virtual machine images come in different formats, some of which are described below." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:19(term) -msgid "Raw" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:26(para) -msgid "We don't recommend creating raw images by dd'ing block device files, we discuss how to create raw images later." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:20(para) -msgid "The \"raw\" image format is the simplest one, and is natively supported by both KVM and Xen hypervisors. You can think of a raw image as being the bit-equivalent of a block device file, created as if somebody had copied, say, /dev/sda to a file using the command. " -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:32(term) ./doc/image-guide/ch_converting.xml:26(literal) -msgid "qcow2" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:37(para) -msgid "Using sparse representation, so the image size is smaller." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:40(para) -msgid "Support for snapshots." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:33(para) -msgid "The 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.xml:43(para) -msgid "Because qcow2 is sparse, qcow2 images are typically smaller than raw images. Smaller images mean faster uploads, so it's often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:46(para) -msgid "Because raw images don't support snapshots, OpenStack Compute will automatically convert raw image files to qcow2 as needed." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:52(term) -msgid "AMI/AKI/ARI" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:58(para) -msgid "AMI (Amazon Machine Image):" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:59(para) -msgid "This is a virtual machine image in raw format, as described above." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:63(para) -msgid "AKI (Amazon Kernel Image)" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:64(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.xml:71(para) -msgid "ARI (Amazon Ramdisk Image)" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:72(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.xml:53(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.xml:80(term) -msgid "UEC tarball" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:83(para) -msgid "Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud Infrastructure." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:81(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.xml:89(term) -msgid "VMDK" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:90(para) -msgid "VMware's ESXi hypervisor uses the VMDK (Virtual Machine Disk) format for images." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:95(term) -msgid "VDI" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:96(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.xml:103(term) -msgid "VHD" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:104(para) -msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:107(term) -msgid "VHDX" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:108(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.xml:114(term) -msgid "OVF" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:115(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.xml:121(para) -msgid "An OVF package can be distributed in different ways. For example, it could be distributed as a set of discrete files, or as a tar archive file with an .ova (open virtual appliance/application) extension." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:124(para) -msgid "OpenStack Compute does not currently have support for OVF packages, so you will need to extract the image file(s) from an OVF package if you wish to use it with OpenStack." -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:129(term) -msgid "ISO" -msgstr "" - -#: ./doc/image-guide/ch_introduction.xml:130(para) -msgid "The 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 "" - -#. 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_freebsd-example.xml:159(None) -msgid "@@image: 'figures/freebsd-partitions.png'; md5=47dbba18dda83b095f370a71e1dc3413" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:11(title) -msgid "Example: FreeBSD image" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:12(para) -msgid "This example creates a minimal FreeBSD image that is compatible with OpenStack and bsd-cloudinit. The bsd-cloudinit program is independently maintained and in active development. The best source of information on the current state of the project is at http://pellaeon.github.io/bsd-cloudinit/." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:20(para) -msgid "KVM with virtio drivers is used as the virtualization platform because that is the most widely used among OpenStack operators. If you use a different platform for your cloud virtualization, use that same platform in the image creation step." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:24(para) -msgid "This example shows how to create a FreeBSD 10 image. To create a FreeBSD 9.2 image, follow these steps with the noted differences." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:28(title) -msgid "To create a FreeBSD image" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:30(para) -msgid "Make a virtual drive:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:32(para) -msgid "The minimum supported disk size for FreeBSD is 1GB. Because the goal is to make the smallest possible base image, the example uses that minimum size. This size is sufficient to include the optional doc, games, and lib32 collections. To include the ports collection, add another 1GB. To include src, add 512MB." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:42(para) -msgid "Get the installer ISO:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:48(para) -msgid "Launch a VM on your local workstation. Use the same hypervisor, virtual disk, and virtual network drivers as you use in your production environment." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:51(para) -msgid "The following command uses the minimum amount of RAM, which is 256MB:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:56(para) -msgid "You can specify up to 1GB additional RAM to make the installation process run faster." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:58(para) -msgid "This VM must also have Internet access to download packages." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:61(para) -msgid "By using the same hypervisor, you can ensure that you emulate the same devices that exist in production. However, if you use full hardware virtualization instead of paravirtualization, you do not need to use the same hypervisor; you must use the same type of virtualized hardware because FreeBSD device names are related to their drivers. If the name of your root block device or primary network interface in production differs than the names used during image creation, errors can occur." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:71(para) -msgid "You now have a VM that boots from the downloaded install ISO and is connected to the blank virtual disk that you created previously." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:76(para) -msgid "To install the operating system, complete the following steps inside the VM:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:80(para) -msgid "When prompted, choose to run the ISO in Install mode." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:84(para) -msgid "Accept the default keymap or select an appropriate mapping for your needs." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:88(para) -msgid "Provide a host name for your image. If you use bsd-cloudinit, it overrides this value with the name provided by OpenStack when an instance boots from this image." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:94(para) -msgid "When prompted about the optional doc, games, lib32, ports, and src system components, select only those that you need. It is possible to have a fully functional installation without selecting additional components selected. As noted previously, a minimal system with a 1GB virtual disk supports doc, games, and lib32 inclusive. The ports collection requires at least 1GB additional space and possibly more if you plan to install many ports. The src collection requires an additional 512MB." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:110(para) -msgid "Configure the primary network interface to use DHCP. In this example, which uses a virtio network device, this interface is named vtnet0." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:115(para) -msgid "Accept the default network mirror." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:118(para) -msgid "Set up disk partitioning." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:119(para) -msgid "Disk partitioning is a critical element of the image creation process and the auto-generated default partitioning scheme does not work with bsd-cloudinit at this time." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:124(para) -msgid "Because the default does not work, you must select manual partitioning. The partition editor should list only one block device. If you use virtio for the disk device driver, it is named vtbd0. Select this device and run the command three times:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:132(para) -msgid "Select Create to create a partition table. This action is the default when no partition table exists. Then, select GPT GUID Partition Table from the list. This choice is the default." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:141(para) -msgid "First partition: A 64kB freebsd-boot partition with no mount point." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:146(para) -msgid "Second partition: A freebsd-ufs partition with a mount point of / with all remaining free space." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:139(para) -msgid "Create two partitions:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:154(para) -msgid "The following figure shows a completed partition table with a 1GB virtual disk:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:162(para) -msgid "Select Finish and then Commit to commit your changes." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:166(para) -msgid "If you modify this example, the root partition, which is mounted on /, must be the last partition on the drive so that it can expand at run time to the disk size that your instance type provides. Also note that bsd-cloudinit currently has a hard-coded assumption that this is the second partition." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:178(para) -msgid "Select a root password." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:181(para) -msgid "Select the CMOS time zone." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:182(para) -msgid "The virtualized CMOS almost always stores its time in UTC, so unless you know otherwise, select UTC." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:186(para) -msgid "Select the time zone appropriate to your environment." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:190(para) -msgid "From the list of services to start on boot, you must select ssh. Optionally, select other services." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:195(para) -msgid "Optionally, add users." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:196(para) -msgid "You do not need to add users at this time. The bsd-cloudinit program adds a freebsd user account if one does not exist. The ssh keys for this user are associated with OpenStack. To customize this user account, you can create it now. For example, you might want to customize the shell for the user." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:205(para) -msgid "Final config" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:206(para) -msgid "This menu enables you to update previous settings. Check that the settings are correct, and click exit." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:211(para) -msgid "After you exit, you can open a shell to complete manual configuration steps. Select Yes to make a few OpenStack-specific changes:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:216(para) -msgid "Set up the console:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:218(para) -msgid "This sets console output to go to the serial console, which is displayed by , and the video console for sites with VNC or Spice configured." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:224(para) -msgid "Minimize boot delay:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:228(para) -msgid "Download the latest bsd-cloudinit-installer. The download commands differ between FreeBSD 10.1 and 9.2 because of differences in how the command handles HTTPS URLs." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:233(para) -msgid "In FreeBSD 10.1 the command verifies SSL peers by default, so you need to install the ca_root_nss package that contains certificate authority root certificates and tell where to find them. For FreeBSD 10.1 run these commands:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:242(para) -msgid "FreeBSD 9.2 does not support peer-verification for https. For FreeBSD 9.2, run this command:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:248(para) -msgid "Run the installer:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:250(para) -msgid "Issue this command to download and install the latest bsd-cloudinit package, and install the necessary prerequisites." -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:255(para) -msgid "Install sudo and configure the freebsd user to have passwordless access:" -msgstr "" - -#: ./doc/image-guide/section_freebsd-example.xml:264(para) -msgid "Power off the system:" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:8(title) -msgid "OpenStack Virtual Machine Image Guide" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:10(titleabbrev) -msgid "VM Image Guide" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:18(orgname) ./doc/image-guide/bk-imageguide.xml:25(holder) -msgid "OpenStack Foundation" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:22(year) -msgid "2013" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:23(year) -msgid "2014" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:24(year) -msgid "2015" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:27(releaseinfo) -msgid "current" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:28(productname) -msgid "OpenStack" -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:32(remark) -msgid "Remaining licensing details are filled in by the template." -msgstr "" - -#: ./doc/image-guide/bk-imageguide.xml:37(para) -msgid "This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack." -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/ch_creating_images_manually.xml:83(None) -msgid "@@image: 'figures/virt-manager-new.png'; md5=4faa75d3058f6a332c01dc1dba9cecbc" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:11(title) -msgid "Create images manually" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:12(para) -msgid "Creating a new image is a step done outside of your OpenStack installation. You create the new image manually on your own system and then upload the image to your cloud." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:16(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 or VirtualBox), you can use that instead and just convert the file to raw once you are done." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:22(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.xml:35(title) -msgid "Verify the libvirt default network is running" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:36(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.xml:43(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.xml:50(para) -msgid "If the network is not active, start it by doing:" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:54(title) -msgid "Use the virt-manager X11 GUI" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:55(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 that will let you view and interact with the guest's graphical console." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:63(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.xml:74(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.xml:71(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.xml:79(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.xml:88(para) -msgid "When using qcow2 format images you should check the option 'customize before install', go to disk properties and explicitly select the qcow2 format. This ensures the virtual machine disk size will be correct." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:96(title) -msgid "Use virt-install and connect by using a local VNC client" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:98(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.xml:106(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.xml:121(para) -msgid "The following example shows how to use the command to create an empty image file, and command to start up a virtual machine using that image file. As root:" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:155(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.xml:138(para) -msgid "The KVM hypervisor starts the virtual machine with the libvirt name, centos-6.4, with 1024MB 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 10GB 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.xml:164(para) -msgid "Run the command to see a range of allowed --os-variant options." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:168(replaceable) -msgid "vm-name" -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:167(para) -msgid "Use the command to get the VNC port number." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_manually.xml:172(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 a VNC client running on your local machine to display :1 on the remote machine and step through the installation process." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:7(title) -msgid "Disk and container formats for images" -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:9(para) -msgid "When you add an image to the Image service, you can specify its disk and container formats." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:12(title) -msgid "Disk formats" -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:13(para) -msgid "The disk format of a virtual machine image is the format of the underlying disk image. Virtual appliance vendors have different formats for laying out the information contained in a virtual machine disk image." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:17(para) -msgid "Set the disk format for your image to one of the following values:" -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:21(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.xml:26(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.xml:32(para) -msgid "vmdk: Common disk format supported by many common virtual machine monitors." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:37(para) -msgid "vdi: Supported by VirtualBox virtual machine monitor and the QEMU emulator." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:42(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.xml:47(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.xml:52(para) -msgid "aki: An Amazon kernel image." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:56(para) -msgid "ari: An Amazon ramdisk image." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:60(para) -msgid "ami: An Amazon machine image." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:66(title) -msgid "Container formats" -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:67(para) -msgid "The container format indicates whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:71(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.xml:76(para) -msgid "You can set the container format for your image to one of the following values:" -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:80(para) -msgid "bare. The image does not have a container or metadata envelope." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:84(para) -msgid "ovf. The OVF container format." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:88(para) -msgid "aki. An Amazon kernel image." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:92(para) -msgid "ari. An Amazon ramdisk image." -msgstr "" - -#: ./doc/image-guide/section_glance_image-formats.xml:96(para) -msgid "ami. An Amazon machine image." -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:7(title) -msgid "Converting between image formats" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:8(para) -msgid "Converting images from one format to another is generally straightforward." -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:10(title) -msgid "qemu-img convert: raw, qcow2, qed, vdi, vmdk, vhd" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:11(para) -msgid "The command can do conversion between multiple formats, including qcow2, qed, raw, vdi, vhd, and vmdk." -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:15(caption) -msgid "qemu-img format strings" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:19(th) -msgid "Image format" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:20(th) -msgid "Argument to qemu-img" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:25(td) -msgid "QCOW2 (KVM, Xen)" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:29(td) -msgid "QED (KVM)" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:30(literal) -msgid "qed" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:33(td) ./doc/image-guide/ch_converting.xml:34(literal) -msgid "raw" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:37(td) -msgid "VDI (VirtualBox)" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:38(literal) -msgid "vdi" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:41(td) -msgid "VHD (Hyper-V)" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:42(literal) -msgid "vpc" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:45(td) -msgid "VMDK (VMware)" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:46(literal) -msgid "vmdk" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:50(para) -msgid "This example will convert a raw image file named centos7.img to a qcow2 image file." -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:54(para) -msgid "Run the following command to convert a vmdk image file to a raw image file. " -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:57(para) -msgid "Run the following command to convert a vmdk image file to a qcow2 image file. " -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:62(para) -msgid "The -f format flag is optional. If omitted, will try to infer the image format." -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:64(para) -msgid "When converting an image file with Windows OS, ensure the virtio driver is installed. Otherwise, you will get a blue screen of death or BSOD when launching the image due to lack of the virtio driver. Another option is to set the image properties as below when you update the image in glance to avoid this issue, but it will reduce performance significantly." -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:74(title) -msgid "VBoxManage: VDI (VirtualBox) to raw" -msgstr "" - -#: ./doc/image-guide/ch_converting.xml:75(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, and Linux, VirtualBox stores images by default in the ~/VirtualBox VMs/ directory. The following example creates a raw image in the current directory from a VirtualBox VDI image." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:11(title) -msgid "Example: Microsoft Windows image" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:12(para) -msgid "This example creates a Windows Server 2012 qcow2 image, using and the KVM hypervisor." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:17(para) -msgid "Follow these steps to prepare the installation:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:20(para) -msgid "Download a Windows Server 2012 installation ISO. Evaluation images are available on the Microsoft website (registration required)." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:26(para) -msgid "Download the signed VirtIO drivers ISO from the Fedora website." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:31(para) -msgid "Create a 15GB qcow2 image:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:37(para) -msgid "Start the Windows Server 2012 installation with the command:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:46(para) -msgid "Use or to connect to the VM and start the Windows installation." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:51(para) -msgid "Enable the VirtIO drivers." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:52(para) -msgid "The disk is not detected by default by the Windows installer. When requested to choose an installation target, click Load driver and browse the file system to select the E:\\WIN8\\AMD64 folder. The Windows installer displays a list of drivers to install. Select the VirtIO SCSI and network drivers, and continue the installation." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:58(para) -msgid "Once the installation is completed, the VM restarts. Define a password for the administrator when prompted." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:62(para) -msgid "Log in as administrator and start a command window." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:65(para) -msgid "Complete the VirtIO drivers installation by running the following command:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:70(para) -msgid "To allow Cloudbase-Init to run scripts during an instance boot, set the PowerShell execution policy to be unrestricted:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:77(para) -msgid "Download and install Cloudbase-Init:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:80(para) -msgid "In the configuration options window, change the following settings:" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:83(para) -msgid "Username: Administrator" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:86(para) -msgid "Network adapter to configure: Red Hat VirtIO Ethernet Adapter" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:90(para) -msgid "Serial port for logging: COM1" -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:93(para) -msgid "When the installation is done, in the Complete the Cloudbase-Init Setup Wizard window, select the Run Sysprep and Shutdown check boxes and click Finish." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:97(para) -msgid "Wait for the machine shutdown." -msgstr "" - -#: ./doc/image-guide/section_windows-example.xml:101(para) -msgid "Your image is ready to upload to the Image service:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:11(title) -msgid "OpenStack Linux image requirements" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:13(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 requirements by installing the cloud-init package. Read this section before you create your own image to be sure that the image supports the OpenStack features that you plan to use." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:23(para) -msgid "Disk partitions and resize root partition on boot (cloud-init)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:27(para) ./doc/image-guide/ch_openstack_images.xml:245(title) -msgid "No hard-coded MAC address information" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:30(para) -msgid "SSH server running" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:33(para) ./doc/image-guide/ch_openstack_images.xml:289(title) -msgid "Disable firewall" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:36(para) -msgid "Access instance using ssh public key (cloud-init)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:40(para) -msgid "Process user data and other metadata (cloud-init)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:44(para) -msgid "Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux kernel version < 3.0)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:50(title) -msgid "Disk partitions and resize root partition on boot (cloud-init)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:52(para) -msgid "When you create a Linux image, you must decide how to partition the disks. The choice of partition method can affect the resizing functionality, as described in the following sections." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:56(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 5GB 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 10GB. When the disk for an instance is resized up, zeros are just added to the end." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:66(para) -msgid "Your image must be able to resize its partitions on boot to match the size requested by the user. Otherwise, after the instance boots, you must manually resize the partitions to access the additional storage to which you have access when the disk size associated with the flavor exceeds the disk size with which your image was created." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:74(title) -msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:76(para) -msgid "If you use the OpenStack XenAPI driver, the Compute service automatically adjusts the partition and file system for your instance on boot. Automatic resize occurs if the following conditions are all true:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:83(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.xml:88(para) -msgid "The disk on the image has only one partition." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:92(para) -msgid "The file system on the one partition is ext3 or ext4." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:96(para) -msgid "Therefore, if you use Xen, we recommend that when you create your images, you create a single ext3 or ext4 partition (not managed by LVM). Otherwise, read on." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:102(title) -msgid "Non-Xen with cloud-init/cloud-tools: One ext3/ext4 partition (no LVM, no /boot, no swap)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:104(para) -msgid "You must configure these items for your image:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:108(para) -msgid "The partition table for the image describes the original size of the image." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:112(para) -msgid "The file system for the image fills the original size of the image." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:116(para) -msgid "Then, during the boot process, you must:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:119(para) -msgid "Modify the partition table to make it aware of the additional space:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:123(para) -msgid "If you do not use LVM, you must modify the table to extend the existing root partition to encompass this additional space." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:129(para) -msgid "If you use LVM, you can add a new LVM entry to the partition table, create a new LVM physical volume, add it to the volume group, and extend the logical partition with the root volume." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:139(para) -msgid "Resize the root volume file system." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:142(para) -msgid "The simplest way to support this is to install in your image the:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:146(para) -msgid "cloud-utils package, which contains the tool for extending partitions." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:151(para) -msgid "cloud-initramfs-growroot package for Ubuntu, Debian and Fedora, which supports resizing root partition on the first boot." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:156(para) -msgid "cloud-initramfs-growroot package for Centos and RHEL." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:160(para) -msgid "cloud-init package." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:164(para) -msgid "With these packages installed, the image performs the root partition resize on boot. For example, in the /etc/rc.local file. These packages are in the Ubuntu and Debian package repository, as well as the EPEL repository (for Fedora/RHEL/CentOS/Scientific Linux guests)." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:171(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.xml:179(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.xml:186(title) -msgid "Non-Xen without cloud-init/cloud-tools: LVM" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:189(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.xml:200(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.xml:207(para) -msgid "Create a new LVM partition with the additional space. For example, ." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:215(replaceable) ./doc/image-guide/ch_openstack_images.xml:222(replaceable) ./doc/image-guide/ch_openstack_images.xml:229(replaceable) -msgid "sda6" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:213(para) -msgid "Create a new physical volume. For example, ." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:221(replaceable) -msgid "vg00" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:218(para) -msgid "Extend the volume group with this physical partition. For example, ." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:228(replaceable) ./doc/image-guide/ch_openstack_images.xml:234(replaceable) -msgid "node-root" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:225(para) -msgid "Extend the logical volume contained the root partition by the amount of space. For example, ." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:232(para) -msgid "Resize the root file system. For example, ." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:198(para) -msgid "Your script must do something like the following:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:237(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.xml:246(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 the instance boots. You should alter the following files:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:256(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.xml:262(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.xml:268(para) -msgid "Remove the HWADDR line from /etc/sysconfig/network-scripts/ifcfg-eth0 on Fedora-based images." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:274(para) -msgid "If you delete the network persistent rules files, you may get a udev kernel warning at boot time, which is why we recommend replacing them with empty files instead." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:281(title) -msgid "Ensure ssh server runs" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:282(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.xml:290(para) -msgid "In general, we recommend that you disable any firewalls inside of your image and use OpenStack security groups to restrict access to instances. The reason is that having a firewall installed on your instance can make it more difficult to troubleshoot networking issues if you cannot connect to your instance." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:298(title) -msgid "Access instance by using ssh public key (cloud-init)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:300(para) -msgid "The typical way that users access virtual machines running on OpenStack is to ssh using public key authentication. For this to work, your virtual machine image must be configured to download the ssh public key from the OpenStack metadata service or config drive, at boot time." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:306(para) -msgid "If both the XenAPI agent and cloud-init are present in an image, cloud-init handles ssh-key injection. The system assumes cloud-init is present when the image has the cloud_init_installed property." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:312(title) -msgid "Use cloud-init to fetch the public key" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:314(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.xml:322(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.xml:332(title) -msgid "Write a custom script to fetch the public key" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:334(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.xml:338(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.xml:378(para) -msgid "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) with - (hyphen). If editing a file over a VNC session, make sure it's http: not http; and authorized_keys not authorized-keys." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:390(title) -msgid "Process user data and other metadata (cloud-init)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:392(para) -msgid "In addition to the ssh public key, an image might need additional information from OpenStack, such as Provide user data to instances, that the user submitted when requesting the image. For example, you might want to set the host name of the instance when it is booted. Or, you might wish to configure your image so that it executes user data content as a script on boot." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:400(para) -msgid "You can access this information through the metadata service or referring to Store metadata on the configuration drive. As the OpenStack metadata service is compatible with version 2009-04-04 of the Amazon EC2 metadata service, consult the Amazon EC2 documentation on Using Instance Metadata for details on how to retrieve user data." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:411(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.xml:418(title) -msgid "Ensure image writes boot log to console" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:419(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.xml:423(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.xml:428(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.xml:437(para) -msgid "Next, update the grub configuration. On Debian-based operating-systems such as Ubuntu, run this command:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:440(para) -msgid "On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this command:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:445(title) -msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:447(para) -msgid "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel did not have support for paravirtualized Xen virtual machine instances (what Xen calls DomU guests). If you are running the Xen hypervisor with paravirtualization, and you want to create an image for an older Linux distribution that has a pre 3.0 kernel, you must ensure that the image boots a kernel that has been compiled with Xen support." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:457(title) -msgid "Manage the image cache" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:458(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.xml:465(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.xml:471(caption) -msgid "Image cache management configuration options" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:477(td) -msgid "Configuration option=Default value" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:478(td) -msgid "(Type) Description" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:483(td) -msgid "preallocate_images=none" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:484(para) -msgid "(StrOpt) VM image preallocation mode:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:487(para) -msgid "none. No storage provisioning occurs up front." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:492(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.xml:509(td) -msgid "remove_unused_base_images=True" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:510(td) -msgid "(BoolOpt) Should unused base images be removed? When set to True, the interval at which base images are removed are set with the following two settings. If set to False base images are never removed by Compute." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:517(td) -msgid "remove_unused_original_minimum_age_seconds=86400" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:518(td) -msgid "(IntOpt) Unused unresized base images younger than this are not removed. Default is 86400 seconds, or 24 hours." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:523(td) -msgid "remove_unused_resized_minimum_age_seconds=3600" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:524(td) -msgid "(IntOpt) Unused resized base images younger than this are not removed. Default is 3600 seconds, or one hour." -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:530(para) -msgid "To see how the settings affect the deletion of a running instance, check the directory where the images are stored:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:534(para) -msgid "In the /var/log/compute/compute.log file, look for the identifier:" -msgstr "" - -#: ./doc/image-guide/ch_openstack_images.xml:541(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/ch_obtaining_images.xml:7(title) -msgid "Get images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:9(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. Most of the images contain the cloud-init package to support SSH key pair and user data injection. Because many of the images disable SSH password authentication by default, boot the image with an injected key pair. You can SSH into the instance with the private key and default login account. See the OpenStack End User Guide for more information on how to create and inject key pairs with OpenStack." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:21(title) -msgid "CentOS images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:22(para) -msgid "The CentOS project maintains official images for direct download." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:28(link) -msgid "CentOS 6 images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:34(link) -msgid "CentOS 7 images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:39(para) -msgid "In a CentOS cloud image, the login account is centos." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:44(title) -msgid "CirrOS (test) images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:45(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 download page." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:54(para) -msgid "In a CirrOS image, the login account is cirros. The password is cubswin:)" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:49(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.4-x86_64-disk.img. " -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:60(title) -msgid "Official Ubuntu images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:61(para) -msgid "Canonical maintains an official set of Ubuntu-based images." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:63(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 14.04 \"Trusty Tahr\" is http://cloud-images.ubuntu.com/trusty/current/. Scroll to the bottom of the page for links to images that can be downloaded directly." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:73(para) -msgid "In an Ubuntu cloud image, the login account is ubuntu." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:69(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 14.04 is trusty-server-cloudimg-amd64-disk1.img." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:78(title) -msgid "Official Red Hat Enterprise Linux images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:79(para) -msgid "Red Hat maintains official Red Hat Enterprise Linux cloud images. A valid Red Hat Enterprise Linux subscription is required to download these images." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:88(link) -msgid "Red Hat Enterprise Linux 7 KVM Guest Image" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:94(link) -msgid "Red Hat Enterprise Linux 6 KVM Guest Image" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:99(para) -msgid "In a RHEL cloud image, the login account is cloud-user." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:106(title) -msgid "Official Fedora images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:110(para) -msgid "In a Fedora cloud image, the login account is fedora." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:107(para) -msgid "The Fedora project maintains a list of official cloud images at . " -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:115(title) -msgid "Official openSUSE and SLES images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:116(para) -msgid "SUSE provides images for openSUSE. For SUSE Linux Enterprise Server (SLES), custom images can be built with a web-based tool called SUSE Studio. SUSE Studio can also be used to build custom openSUSE images." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:122(title) -msgid "Official Debian images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:123(para) -msgid "Since January 2015, Debian provides images for direct download. They are now made at the same time as the CD and DVD images of Debian. However, until Debian 8.0 (aka Jessie) is out, these images are the weekly built images of the testing distribution." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:129(para) -msgid "If you wish to build your own images of Debian 7.0 (aka Wheezy, the current stable release of Debian), you can use the package which is used to build the official Debian images. It is named openstack-debian-images, and it provides a simple script for building them. This package is available in Debian Unstable, Debian Jessie, and through the wheezy-backports repositories. To produce a Wheezy image, simply run: " -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:137(para) -msgid "If building the image for Wheezy, packages like cloud-init, cloud-utils or cloud-initramfs-growroot will be pulled from wheezy-backports. Also, the current version of bootlogd in Wheezy doesn't support logging to multiple consoles, which is needed so that both the OpenStack Dashboard console and the console works. However, a fixed version is available from the non-official GPLHost repository. To install it on top of the image, it is possible to use the option of the script, with this kind of script as parameter: " -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:157(para) -msgid "In a Debian image, the login account is admin." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:161(title) -msgid "Official images from other Linux distributions" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:162(para) -msgid "As of this writing, we are not aware of other distributions that provide images for download." -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:165(title) -msgid "Rackspace Cloud Builders (multiple distros) images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:167(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.xml:173(title) -msgid "Microsoft Windows images" -msgstr "" - -#: ./doc/image-guide/ch_obtaining_images.xml:174(para) -msgid "Cloudbase Solutions hosts an OpenStack Windows Server 2012 Standard Evaluation image that runs on Hyper-V, KVM, and XenServer/XCP." -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_ubuntu-example.xml:42(None) -msgid "@@image: 'figures/ubuntu-install.png'; md5=999f5b14528b82401dbe04dce8779f4c" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_ubuntu-example.xml:86(None) -msgid "@@image: 'figures/ubuntu-software-selection.png'; md5=423be828f701345f7d20551a39f24271" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_ubuntu-example.xml:96(None) -msgid "@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/image-guide/section_ubuntu-example.xml:109(None) -msgid "@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:7(title) -msgid "Example: Ubuntu image" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:8(para) -msgid "This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image for a different version of Ubuntu, follow these steps with the noted differences." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:11(title) -msgid "Download an Ubuntu install ISO" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:12(para) -msgid "Because the goal is to make the smallest possible base image, this example uses the network installation ISO. The Ubuntu 64-bit 14.04 network installer ISO is at http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini.iso." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:18(title) -msgid "Start the install process" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:19(para) -msgid "Start the installation process by using either or as described in the previous section. If you use , do not forget to connect your VNC client to the virtual machine." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:23(para) -msgid "Assume that the name of your virtual machine image is ubuntu-14.04, which you need to know when you use commands to manipulate the state of the image." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:26(para) -msgid "If you are using , the commands should look something like this:" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:37(title) ./doc/image-guide/section_ubuntu-example.xml:59(title) -msgid "Step through the install" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:38(para) -msgid "At the initial Installer boot menu, choose the Install option. Step through the install prompts, the defaults should be fine." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:48(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.xml:55(title) -msgid "Select a mirror" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:56(para) -msgid "The default mirror proposed by the installer should be fine." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:60(para) -msgid "Step through the install, using the default options. When prompted for a user name, the default (ubuntu) is fine." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:65(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_ubuntu-example.xml:70(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_ubuntu-example.xml:74(title) -msgid "Automatic updates" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:75(para) -msgid "The Ubuntu installer will ask how you want to manage upgrades on your system. This option depends on your specific use case. If your virtual machine instances will be connected to the Internet, we recommend \"Install security updates automatically\"." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:80(title) -msgid "Software selection: OpenSSH server" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:81(para) -msgid "Choose \"OpenSSH server\" so that you will be able to SSH into the virtual machine when it launches inside of an OpenStack cloud." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:91(title) -msgid "Install GRUB boot loader" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:92(para) -msgid "Select \"Yes\" when asked about installing the GRUB boot loader to the master boot record." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:99(para) -msgid "For more information on configuring Grub, see ." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:104(para) -msgid "Select the defaults for all of the remaining options. When the installation is complete, you will be prompted to remove the CD-ROM." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:113(para) -msgid "There is a known bug in Ubuntu 14.04; when you select \"Continue\", the virtual machine will shut down, even though it says it will reboot." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:117(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_ubuntu-example.xml:134(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.xml:141(para) -msgid "In the previous example, you paused the instance, ejected the disk, and unpaused the instance. In theory, you could have ejected the disk at the Installation complete screen. However, our testing indicates that the Ubuntu installer locks the drive so that it cannot be ejected at that point." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:150(para) -msgid "When you boot for the first time after install, it may ask you about authentication tools, you can just choose 'Exit'. Then, log in as root using the root password you specified." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:155(title) -msgid "Install cloud-init" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:156(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.xml:159(para) -msgid "Install the cloud-init package:" -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:161(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.xml:164(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.xml:169(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_ubuntu-example.xml:172(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.xml:185(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 installation process. However, each time the image boots up, the virtual Ethernet card will have a different MAC address, so this information must be deleted from the configuration file." -msgstr "" - -#: ./doc/image-guide/section_ubuntu-example.xml:197(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_ubuntu-example.xml:204(para) -msgid "The underlying image file that you created with , such as /tmp/trusty.qcow2, is now ready for uploading to the OpenStack Image service." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:11(title) -msgid "Modify images" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:17(para) -msgid "Do not attempt to use these tools to modify an image that is attached to a running virtual machine. These tools are designed to only modify images that are not currently running." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:13(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.xml:23(title) -msgid "guestfish" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:24(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.xml:29(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.xml:39(title) -msgid "Example guestfish session" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:40(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.xml:52(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.xml:66(para) -msgid "This starts a guestfish session. Note that the guestfish prompt looks like a fish: > <fs>." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:69(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.xml:83(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.xml:87(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.xml:94(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.xml:108(para) -msgid "We're done, so we can exit using the command:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:113(title) -msgid "Go further with guestfish" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:114(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.xml:124(title) -msgid "guestmount" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:125(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.xml:129(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.xml:135(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.xml:147(title) -msgid "virt-* tools" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:152(para) -msgid "virt-edit for editing a file inside of an image." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:158(para) -msgid "virt-df for displaying free space inside of an image." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:164(para) -msgid "virt-resize for resizing an image." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:170(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.xml:178(para) -msgid "virt-sparsify for making an image sparse." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:184(para) -msgid "virt-p2v for converting a physical machine to an image that runs on KVM." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:190(para) -msgid "virt-v2v for converting Xen and VMware images to KVM images." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:148(para) -msgid "The libguestfs project has a number of other useful tools, including:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:197(title) -msgid "Modify a single file inside of an image" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:198(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.xml:215(title) -msgid "Resize an image" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:216(para) -msgid "Here is an example of how to use to resize an image. Assume we have a 16GB Windows image in qcow2 format that we want to resize to 50GB. First, we use to identify the partitions:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:228(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.xml:262(title) -msgid "Loop devices, kpartx, network block devices" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:266(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.xml:263(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.xml:276(title) -msgid "Mount a raw image (without LVM)" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:277(para) -msgid "If you have a raw virtual machine image that is not using LVM to manage its partitions, use the command to find an unused loop device. " -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:283(para) -msgid "In this example, /dev/loop0 is free. Associate a loop device with the raw image:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:286(para) -msgid "If the image only has a single partition, you can mount the loop device directly:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:289(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.xml:295(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.xml:310(title) -msgid "Mount a raw image (with LVM)" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:311(para) -msgid "If your partitions are managed with LVM, use losetup and kpartx as in the previous example to expose the partitions to the host." -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:318(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.xml:328(para) -msgid "Clean up when you're done:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:335(title) -msgid "Mount a qcow2 image (without LVM)" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:336(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.xml:341(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.xml:348(para) -msgid "If the image has, say three partitions (/boot, /, swap), there should be one new device created for each partition:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:357(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.xml:364(para) -msgid "If the image partitions are not managed with LVM, they can be mounted directly:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:368(para) -msgid "When you're done, clean up:" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:373(title) -msgid "Mount a qcow2 image (with LVM)" -msgstr "" - -#: ./doc/image-guide/ch_modifying_images.xml:374(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.xml:388(para) -msgid "When you're done, clean up:" -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:7(title) -msgid "Image metadata" -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:9(para) -msgid "Image metadata can help end users determine the nature of an image, and is used by associated OpenStack components and drivers which interface with the Image service." -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:11(para) -msgid "Metadata can also determine the scheduling of hosts. If the option is set on an image, and Compute is configured so that the ImagePropertiesFilter scheduler filter is enabled (default), then the scheduler only considers compute hosts that satisfy that property." -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:15(para) -msgid "Compute's ImagePropertiesFilter value is specified in the value in the /etc/nova/nova.conf file." -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:18(para) -msgid "You can add metadata to Image service images by using the --property key=value parameter with the or command. More than one property can be specified. For example:" -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:22(replaceable) -msgid "img-uuid" -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:23(para) -msgid "Common image properties are also specified in the /etc/glance/schema-image.json file. For a complete list of valid property keys and values, refer to the OpenStack Command-Line Reference." -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:28(para) -msgid "All associated properties for an image can be displayed using the command. For example:" -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:71(title) -msgid "Volume-from-Image properties" -msgstr "" - -#: ./doc/image-guide/section_glance-image-metadata.xml:72(para) -msgid "When creating Block Storage volumes from images, also consider your configured image properties. If you alter the core image properties, you should also update your Block Storage configuration. Amend in the /etc/cinder/cinder.conf file on all controller nodes to match the core properties you have set in the Image service." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:8(title) -msgid "Example: Fedora image" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:9(para) -msgid "Download a Fedora ISO image. This procedure lets you create a Fedora 20 image." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:12(para) -msgid "Start the installation using as shown below:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:20(para) -msgid "This will launch a VM and start the installation process." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:41(para) -msgid "Choose the VNC or text mode to set the installation options." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:52(para) -msgid "Set the timezone, network configuration, installation source, and the root password. Optionally, you can choose to create a user." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:55(para) -msgid "Set up the installation destination as shown below:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:113(para) -msgid "Run the following commands from the host to eject the disk and reboot using virsh, as root." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:115(replaceable) -msgid "fedora-20" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:118(para) -msgid "You can also use the GUI to detach and reboot it by manually stopping and starting." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:120(para) -msgid "Log in as root user when you boot for the first time after installation." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:122(para) -msgid "Install and run the acpid service on the guest system to enable the virtual machine to reboot or shutdown an instance." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:124(para) -msgid "Run the following commands inside the Fedora guest to install the ACPI service and configure it to start when the system boots:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:128(para) -msgid "Install cloud-init package inside the Fedora guest by adding the EPEL repo:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:130(para) -msgid "The cloud-init package automatically fetches the public key from the metadata server and places the key in an account." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:134(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, add this line to the configuration file:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:140(para) -msgid "Disable the default zeroconf route for the instance to access the metadata service:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:143(para) -msgid "For the command to work properly on Fedora 20, you might need to add the following lines to the /boot/grub/menu.lst file:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:150(para) -msgid "Shut down the instance from inside the instance as a root user:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:152(para) -msgid "Clean up and remove MAC address details." -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:159(para) -msgid "Use the virt-sysprep utility. This performs various cleanup tasks such as removing the MAC address references. It will clean up a virtual machine image in place:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:163(para) -msgid "Undefine the domain since you no longer need to have this virtual machine image managed by libvirt:" -msgstr "" - -#: ./doc/image-guide/section_fedora-example.xml:167(para) -msgid "The underlying image file that you created with qemu-img create is ready to be uploaded to the Image service." -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./doc/image-guide/section_fedora-example.xml:0(None) -msgid "translator-credits" -msgstr "" - diff --git a/doc/image-guide/locale/ja.po b/doc/image-guide/locale/ja.po deleted file mode 100644 index 17806684b3..0000000000 --- a/doc/image-guide/locale/ja.po +++ /dev/null @@ -1,4049 +0,0 @@ -# Translators: -# Andreas Jaeger , 2014-2015 -# Tom Fifield , 2015 -# Tomoyuki KATO , 2013-2015 -# -# -# Akihiro Motoki , 2015. #zanata -# KATO Tomoyuki , 2015. #zanata -# OpenStack Infra , 2015. #zanata -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-11-16 05:58+0000\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-11-15 04:46+0000\n" -"Last-Translator: Akihiro Motoki \n" -"Language: ja\n" -"Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Zanata 3.7.1\n" -"Language-Team: Japanese\n" - -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 "" -"(論理型) 未使用のイメージが削除されるかどうかです。True (真) に設定した場合、" -"ベースイメージが削除される間隔は、以下の 2 つの設定で設定されます。False " -"(偽) に設定した場合、ベースイメージは Compute により削除されません。" - -msgid "" -"(IntOpt) Unused resized base images younger than this are not removed. " -"Default is 3600 seconds, or one hour." -msgstr "" -"(整数型) この時間内は、未使用かつ容量変更のあるベースイメージが削除されませ" -"ん。デフォルトは 3600 秒 (1 時間) です。" - -msgid "" -"(IntOpt) Unused unresized base images younger than this are not removed. " -"Default is 86400 seconds, or 24 hours." -msgstr "" -"(整数型) この時間内は、未使用かつ容量変更のないベースイメージが削除されませ" -"ん。デフォルトは 86400 秒 (24 時間) です。" - -msgid "(StrOpt) VM image preallocation mode:" -msgstr "(文字列型) 仮想マシンイメージの事前割り当てのモード:" - -msgid "(Type) Description" -msgstr "(型) 説明" - -msgid "..." -msgstr "..." - -msgid "2013" -msgstr "2013" - -msgid "2014" -msgstr "2014" - -msgid "2015" -msgstr "2015" - -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 "" -"OVF (Open Virtualization Format) は、" -"Distributed Management Task Force (DMTF) 標準化グループにより定義された、仮想" -"マシンのパッケージ形式です。OVF パッケージは、1 つ以上のイメージファイル、仮" -"想マシンに関する情報を含む .ovf XML メタデータファイルを含みます。場合により" -"これ以外のファイルも含みます。" - -msgid "" -"Diskimage-builder is an automated disk image creation tool that " -"supports a variety of distributions and architectures. Diskimage-builder " -"(DIB) can build images for Fedora, Red Hat Enterprise Linux, Ubuntu, Debian, " -"CentOS, and openSUSE. DIB is organized in a series of elements that build on " -"top of each other to create specific images." -msgstr "" -"Diskimage-builder は、さまざまな種類のディストリビューションやアー" -"キテクチャーをサポートする、ディスクイメージの自動作成ツールです。diskimage-" -"builder (DIB) は、Fedora、Red Hat Enterprise Linux、Ubuntu、Debian、CentOS、" -"openSUSE のイメージを作成できます。DIB は、エレメント群に分類されており、エレ" -"メントを組み合わせて特定のイメージを作成します。" - -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 "" -"imagefactory は、さまざまなク" -"ラウドプロバイダー向けのイメージの構築、変換、アップロードを自動化するために" -"設計された、比較的新しいツールです。バックエンドとして Oz を使用し、" -"OpenStack ベースのクラウドに対応しています。" - -msgid "" -"virt-df for " -"displaying free space inside of an image." -msgstr "" -"virt-df は、" -"イメージ内の空き容量を表示できます。" - -msgid "" -"virt-edit " -"for editing a file inside of an image." -msgstr "" -"virt-edit " -"は、イメージ内のファイルを編集できます。" - -msgid "" -"virt-resize for resizing an image." -msgstr "" -"virt-resize は、イメージの容量を変更できます。" - -msgid "" -"virt-" -"sparsify for making an image sparse." -msgstr "" -"virt-" -"sparsify は、イメージをスパース化できます。" - -msgid "" -"virt-sysprep for preparing an image for distribution (for example, delete SSH host " -"keys, remove MAC address info, or remove user accounts)." -msgstr "" -"virt-sysprep は、イメージを配布する準備ができます (例えば、SSH ホスト鍵の削除、MAC " -"アドレス情報の削除、ユーザーアカウントの削除)。" - -msgid "" -"virt-p2v for " -"converting a physical machine to an image that runs on KVM." -msgstr "" -"virt-p2v は、物理" -"マシンを KVM で動作するイメージに変換できます。" - -msgid "" -"virt-v2v for " -"converting Xen and VMware images to KVM images." -msgstr "" -"virt-v2v は、Xen " -"や VMware のイメージを KVM のイメージに変換できます。" - -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 "" -"SUSE Studio は、ソフトウェ" -"アアプリケーションを Web ブラウザーで構築、テストするための Web アプリケー" -"ションです。物理、仮想、クラウドベースのアプリケーションの作成をサポートして" -"います。ディストリビューションとして SUSE Linux Enterprise と openSUSE を使用" -"した OpenStack ベースのクラウド用のイメージを構築できます。" - -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 "" -"Oz は、仮" -"想マシンイメージファイルの作成手順を自動化するコマンドラインツールです。 Oz " -"は 、KVM とやり取りを行う Python アプリケーションで、仮想マシンのインストール" -"手順を順に行います。サポートするオペレーティングシステム用の事前定義された " -"kickstart (Red Hat 系システム)、preseed ファイル (Debian 系システム) を使用し" -"ます。Microsoft Windows イメージを作成するためにも使用できます。Fedora の場" -"合、yum を用いて Oz をインストールします。" - -msgid "" -" VeeWee is " -"often used to build Vagrant " -"boxes, but it can also be used to build KVM images." -msgstr "" -" VeeWee は、" -"よく Vagrant ボックスを構築" -"するのに使用されますが、KVM イメージを構築するためにも使用できます。" - -msgid "" -"cloud-init " -"package." -msgstr "" -"cloud-init パッ" -"ケージ。" - -msgid "" -"cloud-" -"initramfs-growroot package for Ubuntu, Debian and Fedora, which " -"supports resizing root partition on the first boot." -msgstr "" -"Ubuntu、Debian、Fedora の場合、cloud-initramfs-growroot パッケージ。最初に起" -"動するルートパーティションの容量を変更できます。" - -msgid "" -"cloud-utils " -"package, which contains the tool for extending partitions." -msgstr "" -"cloud-utils " -"パッケージ。パーティションを拡張するための ツールを含みま" -"す。" - -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 "" -"VMBuilder " -"(Virtual Machine Builder) は、さまざまなハイパーバイザー向けの仮想マシンイ" -"メージを作成するコマンドラインツールです。Ubuntu に同梱されている VMBuilder " -"のバージョンは、Ubuntu 仮想マシンゲストのみを作成できます。Debian に同梱され" -"ている VMBuilder のバージョンは、Ubuntu と Debian の仮想マシンゲストを作成で" -"きます。" - -msgid "" -" Packer is a tool for creating " -"machine images for multiple platforms from a single source configuration." -msgstr "" -" Packer は、単一の設定ファイル" -"から複数のプラットフォーム向けのマシンイメージを作成するツールです。" - -msgid "aki. An Amazon kernel image." -msgstr "aki。Amazon カーネルイメージ。" - -msgid "aki: An Amazon kernel image." -msgstr "aki: Amazon カーネルイメージ。" - -msgid "ami. An Amazon machine image." -msgstr "ami。Amazon マシンイメージ。" - -msgid "ami: An Amazon machine image." -msgstr "ami: Amazon マシンイメージ。" - -msgid "ari. An Amazon ramdisk image." -msgstr "ari。Amazon ラムディスクイメージ。" - -msgid "ari: An Amazon ramdisk image." -msgstr "ari: Amazon ラムディスクイメージ。" - -msgid "" -"auto_disk_config=True is set as a property on the image " -"in the image registry." -msgstr "" -"auto_disk_config=True が、イメージレジストリーにあるイメー" -"ジのプロパティとして設定されている。" - -msgid "" -"bare. The image does not have a container or metadata " -"envelope." -msgstr "" -"bare。コンテナーやメタデータを持たないイメージです。" - -msgid "" -"iso: An archive format for the data contents of an " -"optical disc, such as CD-ROM." -msgstr "" -"iso: CD-ROM などの光学ディスクのデータ向けアーカイブ形式。" - -msgid "none. No storage provisioning occurs up front." -msgstr "" -"none。ストレージの事前プロビジョニングがありません。" - -msgid "ovf. The OVF container format." -msgstr "ovf。OVF コンテナー形式です。" - -msgid "" -"qcow2: Supported by the QEMU emulator that can expand " -"dynamically and supports Copy on Write." -msgstr "" -"qcow2: QEMU エミュレーターによりサポートされます。動的に拡" -"張でき、コピーオンライトをサポートします。" - -msgid "" -"raw: An unstructured disk image format; if you have a " -"file without an extension it is possibly a raw format." -msgstr "" -"raw: 構造化されていないディスクイメージ形式。拡張子のない" -"ファイルは、おそらく raw 形式です。" - -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 "" -"space。ストレージはインスタンスの起動時に完全に割り当てら" -"れます。$instance_dir/ のイメージが fallocate され、十分な空き領域が利用できるかをすぐに判断します。ま" -"た、動作中の割り当てを避け、ブロック割り当てのより良い局所性により、仮想マシ" -"ン I/O パフォーマンスを改善するでしょう。" - -msgid "" -"vdi: Supported by VirtualBox virtual machine monitor and " -"the QEMU emulator." -msgstr "" -"vdi: VirtualBox 仮想マシンモニターと QEMU エミュレーターに" -"よりサポートされます。" - -msgid "" -"vhd: The VHD disk format, a common disk format used by " -"virtual machine monitors from VMware, Xen, Microsoft, VirtualBox, and others." -msgstr "" -"vhd: VHD ディスク形式。VMware、Xen、Microsoft、VirtualBox " -"などのハイパーバイザーにより使用される一般的なディスク形式。" - -msgid "" -"vmdk: Common disk format supported by many common virtual " -"machine monitors." -msgstr "" -"vmdk: 数多くの一般的なハイパーバイザーによりサポートされる" -"一般的なディスク形式。" - -msgid "" -"cloud-initramfs-growroot package for Centos and RHEL." -msgstr "" -"CentOS、RHEL の場合、cloud-initramfs-growroot パッケージ。" - -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 "" -" は、イメージをローカルファイルシステムに直接マウントしませ" -"ん。代わりに、ファイルを表示、編集、削除するためのシェルインターフェースを提" -"供します。、、 など、多くの " -" コマンドは、伝統的な bash コマンドに似ています。" - -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 "" -" HWADDR 行を削除するために、 " -"ifcfg-eth0 ファイルを編集したいです。 コ" -"マンドは、ファイルをホストにコピーし、エディターを実行し、ファイルを書き戻し" -"ます。" - -#. 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. -msgid "" -"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" -msgstr "" -"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" - -#. 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. -msgid "" -"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" -msgstr "" -"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" - -#. 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. -msgid "" -"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" -msgstr "" -"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" - -#. 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. -msgid "" -"@@image: 'figures/freebsd-partitions.png'; " -"md5=47dbba18dda83b095f370a71e1dc3413" -msgstr "" -"@@image: 'figures/freebsd-partitions.png'; " -"md5=47dbba18dda83b095f370a71e1dc3413" - -#. 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. -msgid "" -"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" -msgstr "" -"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" -msgstr "" -"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" -msgstr "" -"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-install.png'; md5=999f5b14528b82401dbe04dce8779f4c" -msgstr "" -"@@image: 'figures/ubuntu-install.png'; md5=999f5b14528b82401dbe04dce8779f4c" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-software-selection.png'; " -"md5=423be828f701345f7d20551a39f24271" -msgstr "" -"@@image: 'figures/ubuntu-software-selection.png'; " -"md5=423be828f701345f7d20551a39f24271" - -#. 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. -msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" -msgstr "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" - -#. 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. -msgid "" -"@@image: 'figures/virt-manager-new.png'; md5=4faa75d3058f6a332c01dc1dba9cecbc" -msgstr "" -"@@image: 'figures/virt-manager-new.png'; md5=4faa75d3058f6a332c01dc1dba9cecbc" - -msgid "" -"A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains " -"an AMI file, AKI file, and ARI file." -msgstr "" -"UEC (Ubuntu Enterprise Cloud) ファイルは、AMI ファイル、AKI ファイル、ARI " -"ファイルを含む、gzip された tar ファイルです。" - -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 "" -"Oz の詳細は、このドキュメントの範囲を超えていますが、例を挙げておきます。" -"GitHub の rackerjoe/oz-image-build/templates にも Oz テ" -"ンプレートの例があります。以下は、Oz を用いて CentOS 6.4 イメージを作成する方" -"法です。" - -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 "" -"ハイパーバイザーがイメージを起動するために最初に読み込むカーネルファイル。" -"Linux の場合、これは vmlinuz でしょう。" - -msgid "" -"A virtual machine image is a single file which contains a virtual disk that " -"has a bootable operating system installed on it." -msgstr "" -"仮想マシンイメージは、ブート可能なオペレーティングシステムがインストールされ" -"た仮想ディスクを格納した、単一のファイルです。" - -msgid "AKI (Amazon Kernel Image)" -msgstr "AKI (Amazon Kernel Image)" - -msgid "AMI (Amazon Machine Image):" -msgstr "AMI (Amazon Machine Image):" - -msgid "AMI/AKI/ARI" -msgstr "AMI/AKI/ARI" - -msgid "ARI (Amazon Ramdisk Image)" -msgstr "ARI (Amazon Ramdisk Image)" - -msgid "" -"Accept the default keymap or select an appropriate mapping for your needs." -msgstr "" -"デフォルトのキーマップを使用するか、必要に応じて適切なキーマップを選択しま" -"す。" - -msgid "Accept the default network mirror." -msgstr "デフォルトのネットワークミラーを受け入れます。" - -msgid "Access instance by using ssh public key (cloud-init)" -msgstr "SSH 公開鍵を使用したインスタンスへのアクセス (cloud-init)" - -msgid "Access instance using ssh public key (cloud-init)" -msgstr "" -"SSH 公開鍵を使用したインスタンスへのアクセス (cloud-init)" - -msgid "" -"After Oz completes the initial OS install using the kickstart file, it " -"customizes the image with an update. It also removes any reference to the " -"eth0 device that libvirt creates while Oz does the customizing, as specified " -"in the command section of the XML file." -msgstr "" -"kickstart ファイルを使用して OS の初期インストールを終えると、Oz はアップデー" -"トと行うとともにイメージをカスタマイズします。Oz は libvirt が作成する eth0 " -"デバイスへの参照をすべて削除します。また、XML ファイルの command セクションの指定にもとづいてカスタマイズを行います。" - -msgid "" -"After you exit, you can open a shell to complete manual configuration steps. " -"Select Yes to make a few OpenStack-specific changes:" -msgstr "" -"終了後、手動設定ステップを実行するために、シェルを開けます。Yes を選択して、いくつかの OpenStack 固有の変更を実行します。" - -msgid "" -"All associated properties for an image can be displayed using the " -" command. For example:" -msgstr "" -"すべての関連するイメージのプロパティーは、 コマンドを使用して" -"表示できます。例:" - -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 "" -"OVF パッケージは、別の方法でも配布できます。例えば、個々のファイル群として配" -"布できます。または .ova (open virtual appliance/application) 拡張子を持つ " -"tar ファイルとしても配布できます。" - -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 "" -"OpenStack Compute のクラウドは、仮想マシンイメージ (「仮想アプライアンス」と" -"言う人もいます) がなければ、あまり便利ではありません。このガイドでは、" -"OpenStack と互換性のある仮想マシンイメージを取得、作成、編集する方法を説明し" -"ます。" - -msgid "" -"An instance must interact with the metadata service to perform several tasks " -"on start up. For example, the instance must get the ssh public key and run " -"the user data script. To ensure that the instance performs these tasks, use " -"one of these methods:" -msgstr "" -"インスタンスは、起動時にいくつかの処理を実行するために、メタデータサービスと" -"通信する必要があります。例えば、インスタンスが SSH 公開鍵を取得し、ユーザー" -"データエージェントを実行する必要があります。インスタンスが確実にこれらの処理" -"を実行するために、以下の方法のどれかを使用します。" - -msgid "" -"An optional ramdisk file mounted at boot time. For a Linux machine, this " -"would be an initrd file." -msgstr "" -"起動時にマウントされる、オプションの RAM ディスクファイル。Linux の場合、これ" -"は initrd ファイルでしょう。" - -msgid "Argument to qemu-img" -msgstr "qemu-img の引数" - -msgid "" -"As of this writing, there are no Oz packages for Ubuntu, so you will need to " -"either install from the source or build your own .deb file." -msgstr "" -"執筆時点で、Ubuntu 用 Oz パッケージはありません。ソースからインストールする" -"か、自分で .deb ファイルをビルドする必要があります。" - -msgid "" -"As of this writing, we are not aware of other distributions that provide " -"images for download." -msgstr "" -"執筆時点では、ダウンロード用のイメージを提供している他のディストリビューショ" -"ンを把握していません。" - -msgid "" -"As the OpenStack metadata service is compatible with version 2009-04-04 of " -"the Amazon EC2 metadata service, consult the Amazon EC2 documentation on " -"Using Instance Metadata " -"for details on how to get user data." -msgstr "" -"OpenStack メタデータサービスは、Amazon EC2 メタデータサービスの 2009-04-04 版" -"と互換性があります。ユーザーデータの取得方法に関する詳細は Using Instance Metadata にある Amazon EC2 " -"のドキュメントを参照してください。" - -msgid "" -"Assume that the name of your virtual machine image is ubuntu-14.04, which you need to know when you use commands to " -"manipulate the state of the image." -msgstr "" -"仮想マシンイメージの名前が ubuntu-14.04 であると仮定しま" -"す。これは、イメージを操作するために コマンドを使用する際" -"に、知っている必要があります。" - -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 "" -"centos63_desktop.img という名前の CentOS qcow2 イメージ" -"があると仮定します。以下のとおり、root としてイメージを読み書きモードでマウン" -"トします。" - -msgid "Assume that:" -msgstr "以下を前提としています。" - -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 "" -"1 番目のブロックデバイス (/dev/nbd0) が現在未使用である" -"と仮定して、 コマンドと コマンドを使用して、" -"ディスクパーティションを利用できます。root として以下のとおり実行します。" -"" - -msgid "" -"At the initial Installer boot menu, choose the Install or upgrade " -"an existing system option. Step through the installation prompts. " -"Accept the defaults." -msgstr "" -"インストーラーの初期ブートメニューで、Install or upgrade an " -"existing system を選択します。インストールのプロンプトを 1 つずつ" -"実行します。" - -msgid "" -"At the initial Installer boot menu, choose the Install " -"option. Step through the install prompts, the defaults should be fine." -msgstr "" -"インストーラーの初期ブートメニューで、Install を選択しま" -"す。インストールのプロンプトを一つずつ実行します。デフォルトのままが良いで" -"しょう。" - -msgid "Automatic updates" -msgstr "自動更新" - -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 "" -"remove_unused_original_minimum_age_seconds のデフォルト時" -"間は 86400 秒 (24 時間) なので、ベースイメージが削除されたことを確認するため" -"に、その時間待つことができます。または、nova.conf により" -"短い時間を設定します。nova.conf の設定を変更した後、すべ" -"ての nova サービスを再起動してください。" - -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 "" -"VNC は標準的なプロトコルなので、VNC の仕様を実装した複数のクライアントが利用" -"できます。TigerVNC (複数のプラットフォー" -"ム)、TightVNC (複数のプラッ" -"トフォーム)、RealVNC (複数の" -"プラットフォーム)、Chicken (Mac OS X)、Krde (KDE)、Vinagre (GNOME) などがあります。" - -msgid "" -"Because qcow2 is sparse, qcow2 images are typically smaller than raw images. " -"Smaller images mean faster uploads, so it's often faster to convert a raw " -"image to qcow2 for uploading instead of uploading the raw file directly." -msgstr "" -"qcow2 はスパースなので、qcow2 イメージは一般的に raw イメージより小さいです。" -"イメージが小さいということは、アップロードが高速になるということを意味しま" -"す。そのため、 raw ファイルをそのままアップロードする代わりに、アップロード用" -"に raw イメージを qcow2 イメージに変換することがよくあります。" - -msgid "" -"Because raw images don't support snapshots, OpenStack Compute will " -"automatically convert raw image files to qcow2 as needed." -msgstr "" -"raw イメージはスナップショットをサポートしないため、OpenStack Compute は、" -"raw イメージファイルを必要に応じて自動的に qcow2 に変換します。" - -msgid "" -"Because the default does not work, you must select manual partitioning. The " -"partition editor should list only one block device. If you use virtio for " -"the disk device driver, it is named vtbd0. Select this " -"device and run the command three times:" -msgstr "" -"デフォルトが正しく動作しないため、手動パーティションを選択する必要がありま" -"す。パーティションエディターは、ブロックデバイスを 1 つだけ表示します。ディス" -"クのデバイスドライバーに virtio を使用する場合、vtbd0 とい" -"う名前になります。このデバイスを選択し、 コマンドを 3 回実行" -"します。" - -msgid "" -"Because the goal is to make the smallest possible base image, this example " -"uses the network installation ISO. The Ubuntu 64-bit 14.04 network installer " -"ISO is at http://archive.ubuntu." -"com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini." -"iso." -msgstr "" -"目標は利用可能な最小のベースイメージを作成することなので、この例はネットワー" -"クインストール ISO を使用します。Ubuntu 64 ビット 14.04 ネットワークインス" -"トーラー ISO は http://archive." -"ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/" -"mini.iso にあります。" - -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 "" -"libvirt を用いて仮想マシンを作成する前に、libvirt の「default\"」ネットワーク" -"が起動していることを確認します。このネットワークは、仮想マシンが外部のネット" -"ワークに接続できるよう、有効化されている必要があります。このネットワークを起" -"動することにより、Linux ブリッジ (通常 virbr0)、iptables " -"ルール、DHCP サーバーとして動作する dnsmasq が作成されます。" - -msgid "" -"By using the same hypervisor, you can ensure that you emulate the same " -"devices that exist in production. However, if you use full hardware " -"virtualization instead of paravirtualization, you do not need to use the " -"same hypervisor; you must use the same type of virtualized hardware because " -"FreeBSD device names are related to their drivers. If the name of your root " -"block device or primary network interface in production differs than the " -"names used during image creation, errors can occur." -msgstr "" -"同じハイパーバイザーを使用することにより、本番環境にあるデバイスと確実に同じ" -"ものをエミュレートできます。しかしながら、準仮想化の代わりに完全仮想化を使用" -"する場合、同じハイパーバイザーを使用する必要はありません。また、FreeBSD のデ" -"バイス名はデバイスドライバーと関連するため、同じ種類の仮想ハードウェアを使用" -"する必要があります。本番環境のルートブロックデバイスの名前、主ネットワークイ" -"ンターフェースの名前がイメージの作成中に使用した名前と異なる場合、エラーが発" -"生する可能性があります。" - -msgid "" -"Canonical maintains an official set of Ubuntu-based images." -msgstr "" -"Canonical は、Ubuntu " -"ベースの公式イメージをメンテナンスしています。" - -msgid "CentOS 6 images" -msgstr "CentOS 6 イメージ" - -msgid "CentOS 7 images" -msgstr "CentOS 7 イメージ" - -msgid "CentOS directory: centos/6/os/x86_64" -msgstr "CentOS ディレクトリー: centos/6/os/x86_64" - -msgid "CentOS images" -msgstr "CentOS イメージ" - -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 "" -"「OpenSSH server」を選択して、OpenStack クラウド内での起動時に、仮想マシンに " -"SSH ログインできるようにします。" - -msgid "Choose URL as the installation method." -msgstr "インストール方法として URL を選択します。" - -msgid "Choose the VNC or text mode to set the installation options." -msgstr "" -"インストールオプションを設定するために、VNC モードまたはテキストモードを選択" -"します。" - -msgid "CirrOS (test) images" -msgstr "CirrOS (test) イメージ" - -msgid "" -"CirrOS is a minimal Linux distribution that was designed for use as a test " -"image on clouds such as OpenStack Compute. You can download a CirrOS image " -"in various formats from the CirrOS download page." -msgstr "" -"CirrOS は、OpenStack Compute のようなクラウドでテストイメージとして使用するた" -"めに設計された、最小の Linux ディストリビューションです。CirrOS ダウンロードページから " -"CirrOS をさまざまな形式でダウンロードできます。" - -msgid "Clean up (remove MAC address details)" -msgstr "クリーンアップ (MAC アドレスの詳細の削除)" - -msgid "Clean up and remove MAC address details." -msgstr "MAC アドレスの詳細をクリーンアップし、削除します。" - -msgid "Clean up when you're done:" -msgstr "完了後、クリーンアップします。" - -msgid "" -"Click one of the HTTP links in the right-hand column next " -"to one of the mirrors." -msgstr "ミラーの右側にある HTTP リンクをクリックします。" - -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 "" -"画面左上にある「New」ボタンをクリックし、指示にしたがって進めます。" -"仮想マシンに関する情報を指定できる、一連のダイアログボックス" -"が表示されます。" - -msgid "Click the isos/ folder link." -msgstr "isos/ フォルダーへのリンクをクリックします。" - -msgid "Click the x86_64/ folder link for 64-bit images." -msgstr "" -"64 ビットイメージ用の x86_64/ フォルダーへのリンクをクリッ" -"クします。" - -msgid "" -"Click the folder link of the CentOS version that you want to use. For " -"example, 6.4/." -msgstr "" -"使用したい CentOS のバージョンのリンクをクリックします。例えば、6.4/" -" です。" - -msgid "" -"Click the netinstall ISO image that you want to download. For example, " -"CentOS-6.4-x86_64-netinstall.iso is a good choice " -"because it is a smaller image that downloads missing packages from the " -"Internet during installation." -msgstr "" -"ダウンロードしたい netinstall ISO イメージをクリックします。例えば、" -"CentOS-6.4-x86_64-netinstall.iso は小さいイメージなので" -"良いでしょう。不足しているパッケージは、インストール中にインターネットからダ" -"ウンロードされます。" - -msgid "" -"Cloudbase Solutions hosts an OpenStack Windows Server 2012 Standard Evaluation image " -"that runs on Hyper-V, KVM, and XenServer/XCP." -msgstr "" -"Cloudbase Solutions は、Hyper-V、KVM、XenServer/XCP で動作する OpenStack Windows Server 2012 " -"Standard 評価イメージ を配布しています。" - -msgid "" -"Common image properties are also specified in the /etc/glance/" -"schema-image.json file. For a complete list of valid property " -"keys and values, refer to the OpenStack Command-Line Reference." -msgstr "" -"イメージの共通のプロパティも /etc/glance/schema-image.json ファイルに指定されます。有効なキーと値の一覧は、OpenStack コマンドラインリファレンスを参照してください。" - -msgid "" -"Complete the VirtIO drivers installation by running the following command:" -msgstr "" -"以下のコマンドを実行して、VirtIO ドライバーのインストールを完了します。" - -msgid "" -"Compute's ImagePropertiesFilter value is specified " -"in the value in the /etc/nova/nova.conf file." -msgstr "" -"Compute の ImagePropertiesFilter 値は、/" -"etc/nova/nova.conf ファイルの 値に指定されます。" - -msgid "Configuration option=Default value" -msgstr "設定オプション=規定値" - -msgid "Configure TCP/IP" -msgstr "TCP/IP の設定" - -msgid "Configure console" -msgstr "コンソールの設定" - -msgid "" -"Configure the primary network interface to use DHCP. In this example, which " -"uses a virtio network device, this interface is named vtnet0." -msgstr "" -"主ネットワークインターフェースが DHCP を使用するよう設定します。この例では、" -"このインターフェースは vtnet0 という名前で、virtio ネット" -"ワークデバイスを使用します。" - -msgid "Configure to fetch metadata" -msgstr "メタデータ取得の設定" - -msgid "" -"Consider using other mirrors as an alternative to mirror.umd.edu." -msgstr "" -"mirror.umd.edu の代わりに、他のミラーを使用することを考え" -"てください。" - -msgid "Container formats" -msgstr "コンテナー形式" - -msgid "Converting between image formats" -msgstr "イメージ形式の変換" - -msgid "" -"Converting images from one format to another is generally straightforward." -msgstr "イメージをある形式から別の形式に変換することは、一般的に簡単です。" - -msgid "Create a 15GB qcow2 image:" -msgstr "15GB qcow2 イメージを作成します。" - -msgid "" -"Create a new LVM partition with the additional space. For example, " -"." -msgstr "" -"この追加領域を用いて新規 LVM パーティションを作成します。例えば、" -"。" - -msgid "Create a new physical volume. For example, ." -msgstr "新規物理ボリュームを作成します。例えば、。" - -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 "" -"以下の内容のテンプレートファイルを作成します。centos64.tdl という名前にします。変更する必要がある項目は、<" -"rootpw> の内容だけです。" - -msgid "Create images manually" -msgstr "イメージの手動作成" - -msgid "Create two partitions:" -msgstr "2 つのパーティションを作成します。" - -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 "" -"新しいイメージの作成は、OpenStack インストール環境の外部で実行する手順です。" -"お使いのシステムで新しいイメージを手動作成し、そのイメージをクラウドにアップ" -"ロードします。" - -msgid "" -"Depending on the version of CentOS, the net installer requires the user to " -"specify either a URL or the web site and a CentOS directory that corresponds " -"to one of the CentOS mirrors. If the installer asks for a single URL, a " -"valid URL might be http://mirror.umd.edu/centos/6/os/x86_64." -msgstr "" -"CentOS のバージョンによっては、ユーザーが CentOS のミラーに応じた、URL や " -"Web サイト、および CentOS のディレクトリをネットワークインストーラーに指定す" -"る必要があります。インストーラーが URL だけを要求する場合、http://" -"mirror.umd.edu/centos/6/os/x86_64 は有効な URL の 1 つです。" - -msgid "Detach the CD-ROM and reboot" -msgstr "CD-ROM の取り出しと再起動" - -msgid "" -"Detect if any additional space is available on the disk. For example, parse " -"the output of ." -msgstr "" -"ディスクの追加領域を利用可能かどうかを検知します。例えば、 の" -"出力を解析します。" - -msgid "Disable firewall" -msgstr "ファイアウォールの無効化" - -msgid "" -"Disable the default zeroconf route for the instance to " -"access the metadata service:" -msgstr "" -"インスタンスがメタデータサービスにアクセスするために、デフォルトの " -"zeroconf ルートを無効化します。" - -msgid "Disable the zeroconf route" -msgstr "zeroconf ルートの無効化" - -msgid "Disk and container formats for images" -msgstr "イメージのディスク形式とコンテナー形式" - -msgid "Disk formats" -msgstr "ディスク形式" - -msgid "" -"Disk partitioning is a critical element of the image creation process and " -"the auto-generated default partitioning scheme does not work with " -"bsd-cloudinit at this time." -msgstr "" -"ディスクパーティションは、イメージ作成プロセスの重要な要素であり、自動生成さ" -"れるデフォルトのパーティション構成は、今のところ bsd-cloudinit で動作しません。" - -msgid "" -"Disk partitions and resize root partition on boot (cloud-init)" -msgstr "" -"起動時のディスクパーティション設定およびルートパーティションのサイズ変更 " -"(cloud-init)" - -msgid "Disk partitions and resize root partition on boot (cloud-init)" -msgstr "" -"起動時のディスクパーティション設定およびルートパーティションのサイズ変更 " -"(cloud-init)" - -msgid "Diskimage-builder" -msgstr "Diskimage-builder" - -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 "" -"実行中の仮想マシンに接続されているイメージを変更するために、これらのツールを" -"使用しないでください。これらのツールは、動作していないイメージのみを変更する" -"ために設計されています。" - -msgid "" -"Download a Fedora ISO " -"image. This procedure lets you create a Fedora 20 image." -msgstr "" -"Fedora ISO イメージをダウ" -"ンロードします。この手順により、Fedora 20 イメージを作成できます。" - -msgid "Download a CentOS install ISO" -msgstr "CentOS インストール ISO のダウンロード" - -msgid "" -"Download a Windows Server 2012 installation ISO. Evaluation images are " -"available on the Microsoft website (registration " -"required)." -msgstr "" -"Windows Server 2012 インストール ISO をダウンロードします。評価イメージが " -"Microsoft の Web サイトにあります (要登録)。" - -msgid "Download an Ubuntu install ISO" -msgstr "Ubuntu インストール ISO のダウンロード" - -msgid "Download and install Cloudbase-Init:" -msgstr "Cloudbase-Init をダウンロードして、インストールします。" - -msgid "" -"Download the latest bsd-cloudinit-installer. The " -"download commands differ between FreeBSD 10.1 and 9.2 because of differences " -"in how the command handles HTTPS URLs." -msgstr "" -"最新の bsd-cloudinit-installer をダウンロードしま" -"す。ダウンロードのコマンドは、 コマンドが HTTPS URL を処理す" -"る方法が異なるため、FreeBSD 10.1 と 9.2 で異なります。" - -msgid "" -"Download the signed VirtIO drivers ISO from the Fedora " -"website." -msgstr "" -"Fedora の Web サイトから署名" -"付き VirtIO ドライバーの ISO をダウンロードします。" - -msgid "Enable the VirtIO drivers." -msgstr "VirtIO ドライバーを有効化します。" - -msgid "Ensure image writes boot log to console" -msgstr "イメージがブートログをコンソールに書き込むことの確認" - -msgid "Ensure ssh server runs" -msgstr "SSH サーバーの動作確認" - -msgid "Example guestfish session" -msgstr "guestfish 実行例" - -msgid "Example: CentOS image" -msgstr "例: CentOS イメージ" - -msgid "Example: Fedora image" -msgstr "例: Fedora イメージ" - -msgid "Example: FreeBSD image" -msgstr "例: FreeBSD イメージ" - -msgid "Example: Microsoft Windows image" -msgstr "例: Microsoft Windows イメージ" - -msgid "Example: Ubuntu image" -msgstr "例: Ubuntu イメージ" - -msgid "" -"Extend the logical volume contained the root partition by the amount of " -"space. For example, ." -msgstr "" -"ルートパーティションを含む論理ボリュームを合計容量に拡張します。例えば、" -"。" - -msgid "" -"Extend the volume group with this physical partition. For example, " -"." -msgstr "" -"この物理パーティションを用いてボリュームグループを拡張します。例えば、" -"。" - -msgid "Final config" -msgstr "最終設定" - -msgid "First partition: A 64kB freebsd-boot partition with no mount point." -msgstr "" -"1 番目のパーティション: マウントポイントを持たない 64kB freebsd-boot パーティ" -"ション。" - -msgid "Follow these steps to prepare the installation:" -msgstr "以下の手順に沿って、インストールを準備します。" - -msgid "" -"For a Linux-based image to have full functionality in an OpenStack Compute " -"cloud, there are a few requirements. For some of these, you can fulfill the " -"requirements by installing the cloud-init package. " -"Read this section before you create your own image to be sure that the image " -"supports the OpenStack features that you plan to use." -msgstr "" -"Linux イメージが OpenStack クラウドで全機能を利用する場合、いくつかの要件があ" -"ります。これらのいくつかは、cloud-init をインストールすること" -"により、要件を満たせます。イメージを作成する前に、使用する OpenStack の機能を" -"イメージがきちんとサポートするために、このセクションを確認してください。" - -msgid "" -"For example, to mount the root partition from our centos63_desktop." -"qcow2 image to /mnt, we can do:" -msgstr "" -"例えば、centos63_desktop.qcow2 イメージのルートパーティ" -"ションを /mnt にマウントするために、以下のとおり実行しま" -"す。" - -msgid "" -"For information about libvirt images in OpenStack, see The life of an " -"OpenStack libvirt image from Pádraig Brady." -msgstr "" -"OpenStack における libvirt イメージの詳細は、Pádraig Brady 氏の The life " -"of an OpenStack libvirt image を参照してください。" - -msgid "" -"For more information on configuring Grub, see ." -msgstr "" -"Grub 設定の詳細は を参照してください。" - -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 "" -"いくつかの種類の変更の場合、イメージのファイルシステムを直接マウントするほう" -"が簡単かもしれません。libguestfs プロジェクトの プログラムに" -"より実行できます。" - -msgid "" -"For the command to work properly on CentOS 6." -"x, you might need to add the following lines to " -"the /boot/grub/menu.lst file:" -msgstr "" -" コマンドが CentOS 6.x で正しく動" -"作するように、以下の行を /boot/grub/menu.lst ファイルに" -"追加する必要があるでしょう。" - -msgid "" -"For the command to work properly on Fedora 20, you might " -"need to add the following lines to the /boot/grub/menu.lst file:" -msgstr "" -" コマンドが Fedora 20 で正しく動作するために、以下の行を " -"/boot/grub/menu.lst ファイルに追加する必要があるかもしれ" -"ません。" - -msgid "" -"For the instance to access the metadata service, you must disable the " -"default zeroconf route:" -msgstr "" -"インスタンスがメタデータサービスにアクセスできるようにするために、デフォルト" -"の zeroconf ルートを無効化する必要があります。" - -msgid "" -"FreeBSD 9.2 does not support peer-verification for https. " -"For FreeBSD 9.2, run this command:" -msgstr "" -"FreeBSD 9.2 の は、HTTPS の相互検証をサポートしません。" -"FreeBSD 9.2 の場合、このコマンドを実行します。" - -msgid "From inside the instance, as root:" -msgstr "インスタンス内で root として以下を実行します。" - -msgid "" -"From the list of services to start on boot, you must select ssh. Optionally, select other services." -msgstr "" -"ブート時に起動するサービス一覧から、ssh を選択する必要があります。オプションとして、他のサービスを選択で" -"きます。" - -msgid "" -"Further customization could be accomplished by setting environment variables " -"or adding elements to the command-line:" -msgstr "" -"環境変数を設定したり、コマンドラインでエレメントを追加で指定することで、さら" -"にカスタマイズできます。" - -msgid "Get images" -msgstr "イメージの取得" - -msgid "Get the installer ISO:" -msgstr "インストーラーの ISO を取得します。" - -msgid "Go further with guestfish" -msgstr "guestfish のさらなる利用" - -msgid "" -"Here is an example of how to use to resize an image. Assume " -"we have a 16GB Windows image in qcow2 format that we want to resize to 50GB. " -"First, we use to identify the partitions:" -msgstr "" -"これは、イメージの容量を変更するために、 を使用する方法の簡単" -"な例です。容量を 50GB に変更したい、qcow2 形式の 16GB Windows イメージがある" -"と仮定します。まず、パーティションを識別するために使用します。" - -msgid "Hostname" -msgstr "ホスト名" - -msgid "ISO" -msgstr "ISO" - -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 "" -"console=ttyS0 がない場合、GRUB 設定を変更する必要がありま" -"す。一般的に、grub.cfg は自動的に生成されるため、直接編" -"集すべきではありません。代わりに、/etc/default/grub を編" -"集し、GRUB_CMDLINE_LINUX_DEFAULT 変数の値を変更します。" -"" - -msgid "" -"If both the XenAPI agent and cloud-init are present in an " -"image, cloud-init handles ssh-key injection. The system " -"assumes cloud-init is present when the image has the " -"cloud_init_installed property." -msgstr "" -"XenAPI エージェントと cloud-init が両方ともイメージに存在" -"する場合、package>cloud-init が SSH 鍵インジェクションを処理しま" -"す。イメージが cloud_init_installed プロパティーを持つと" -"き、システムは cloud-init が存在すると仮定します。" - -msgid "" -"If building the image for Wheezy, packages like cloud-init, cloud-utils or cloud-initramfs-" -"growroot will be pulled from wheezy-backports. Also, the current " -"version of bootlogd in Wheezy doesn't support logging to " -"multiple consoles, which is needed so that both the OpenStack Dashboard " -"console and the console works. However, a fixed version is available from the " -"non-official GPLHost repository. To install it on top of the image, " -"it is possible to use the option of the " -"script, with this kind of script as parameter: " -msgstr "" -"Wheezy イメージを構築している場合、cloud-init、" -"cloud-utils、cloud-initramfs-growroot " -"のようなパッケージが wheezy バックポートから取得されます。また、Wheezy の " -"bootlogd の最新版は、複数コンソールへのログインをサポート" -"しません。これは OpenStack Dashboard のコンソールと のコン" -"ソールを動作させるために必要になります。しかしながら、修正バージョンが非公式 GPLHost リポジ" -"トリーから取得できます。イメージの上にインストールするために、パラメー" -"ターとしてこの種類のスクリプトを用いて、 スクリプトの " -" オプションを使用できます。" - -msgid "" -"If prompted about which type of devices your installation uses, choose " -"Basic Storage Devices." -msgstr "" -"インストールに使用するデバイスの種類の確認が表示された場合、基本ス" -"トレージデバイス (Basic Storage Devices) を選択します。" - -msgid "" -"If the account you use to ssh into your server does not have permissions to " -"run libvirt, but has sudo privileges, do:" -msgstr "" -"サーバーに SSH するために使用するアカウントが、libvirt を実行する権限を持た" -"ず、sudo 権限を持つ場合、次のとおり実行します。" - -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 "" -"イメージが複数のパーティションを持つ場合、パーティションを別々のデバイス " -"(/dev/mapper/loop0p1) として認識させるために " -" を使用します。そして、ルートファイルシステムに対応するパー" -"ティションをマウントします。" - -msgid "" -"If the image has, say three partitions (/boot, /, swap), there should be one " -"new device created for each partition:" -msgstr "" -"イメージがいわゆる 3 パーティション (/boot、/、swap) を持つ場合、パーティショ" -"ンごとに 1 つの新しいデバイスにすべきです。" - -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 "" -"イメージがいわゆる 3 パーティション (/boot、/、swap) を持つ場合、パーティショ" -"ンごとに 1 つの新しいデバイスにすべきです。 2 番目のパーティ" -"ションをマウントするために、root として次のとおり実行します。" -"完了すると、クリーンアップします。" - -msgid "" -"If the image only has a single partition, you can mount the loop device " -"directly:" -msgstr "" -"イメージがパーティションを一つだけ持つ場合、loop デバイスを直接マウントできま" -"す。" - -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 "" -"イメージのパーティションが LVM で管理されている場合、 と " -" を実行後、マウントできるデバイスとして LVM パーティションを" -"認識するために、 と を使用する必要がありま" -"す。" - -msgid "" -"If the image partitions are not managed with LVM, they can be mounted " -"directly:" -msgstr "" -"イメージのパーティションが LVM で管理されていない場合、直接マウントできます。" - -msgid "" -"If the installer asks for web site name and CentOS directory separately, you " -"might enter:" -msgstr "" -"インストーラーが Web サイト名と CentOS ディレクトリをそれぞれ確認する場合、次" -"のとおり入力します。" - -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 "" -"選択したネットワークブロックデバイスが使用中の場合、最初の " -"コマンドがエラーを表示せず失敗します。そして、/dev/nbd3p{1,2,3} デバイスファイルが作成されません。" - -msgid "If the network is not active, start it by doing:" -msgstr "ネットワークが動作していない場合、以下を実行して起動します。" - -msgid "" -"If unsure, use the default partition scheme for the installer because no " -"scheme is better than another." -msgstr "" -"よくわからない場合、インストーラーのデフォルトのパーティション設定が最良であ" -"るため、そのまま使用します。" - -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 "" -"よくわからない場合、インストーラーのデフォルトのパーティション構成を使用する" -"ことを推奨します。別の構成にする明確な利点がないためです。" - -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 "" -"マウントポイントがゲストのどこであるか不明な場合、guestmount が使用するマウン" -"トポイントを自動的に決定するために、-i (検査) フラグを使用" -"できます。マウントすると、rpm コマンドを使用してインストール" -"済みパッケージを一覧表示するなどの操作を実行できます。完了し" -"たら、アンマウントします。" - -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 "" -"コンソールの無いサーバーにイメージを構築していて、ローカルマシンに X サーバー" -"が有る場合、GUI にアクセスするために、SSH の X11 転送を使用して " -" を起動できます。仮想マシンマネージャーは、libvirt と直接通信" -"するため、アクセスするためには、一般的に root になる必要があります。root (ま" -"たは、libvirt と通信する権限を持つユーザー) として直接 SSH できる場合、次のと" -"おり実行します。" - -msgid "" -"If you are not able to install the cloud-init package in your image, to fetch the ssh public key and add it to " -"the root account, edit the /etc/rc.d/rc.local file and " -"add the following lines before the line touch /var/lock/subsys/" -"local:" -msgstr "" -"cloud-init パッケージをインストー" -"ルできない場合、SSH 公開鍵を取得し、それを root アカウントに追加するために、" -"/etc/rc.d/rc.local ファイルを編集し、touch /" -"var/lock/subsys/local 行の前に以下の行を追加します。" - -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 "" -"ゲスト内に cloud-init をインストールできない場合、したくな" -"い場合は、公開鍵を取得し、ユーザーアカウントに追加するために、カスタムスクリ" -"プトを作成できます。" - -msgid "" -"If you are using , the commands should look something like " -"this:" -msgstr "" -" を使用している場合、このコマンドは以下のようになるでしょう。" - -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 "" -"cloud-utils と cloud-init をインストールできる場合、イメー" -"ジを作成するとき、(LVM により管理されない) 単一の ext3 / ext4 パーティション" -"を作成することを推奨します。" - -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 "" -"cloud-initramfs-tools をインストールできない場合、Robert " -"Plestenjak 氏が linux-rootfs-resize という GitHub プロジェクトを行っていま" -"す。これには、イメージを起動時にリサイズできるよう、 を使用す" -"ることにより、ラムディスクを更新するスクリプトが含まれます。" - -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 "" -"ゲスト内に cloud-init と cloud-tools を" -"インストールできず、リサイズをサポートしたい場合、パーティションテーブルを変" -"更するために、イメージが起動時に実行するスクリプトを書く必要があります。この" -"場合、パーティションを管理するために、LVM を使用することを推奨します。Linux " -"カーネルの制限 (執筆時点) により、現在マウントされているローディスクのパー" -"ティションテーブルを変更できませんが、LVM の場合は実行できます。" - -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 "" -"ネットワーク永続化ルールのファイルを削除すると、起動時に udev カーネルの警告" -"が出るかもしれません。そのため、これらを空ファイルで置き換えることを推奨しま" -"す。" - -msgid "" -"If you do not use LVM, you must modify the table to extend the existing root " -"partition to encompass this additional space." -msgstr "" -"LVM を使用してない場合、既存のルートパーティションをこの追加領域を含むまで拡" -"張するために、テーブルを変更する必要があります。" - -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 "" -"仮想マシンマネージャーを使用したくない場合 (例えば、サーバーに関連パッケージ" -"をインストールしたくない場合、ローカルで X サーバーを動作させていない場合、" -"SSH の X11 転送が動作しない場合)、libvirt から仮想マシンを起動するために " -" ツールを利用できます。また、ローカルマシンにインストールし" -"た VNC クライアントからグラフィカルコンソールに接続できます。" - -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 "" -"libguestfs にアクセスできない場合、loop デバイス、kpartx、ネットワークブロッ" -"クデバイスを使用して、イメージのファイルシステムをホストに直接マウントできま" -"す。" - -msgid "" -"If you have a raw virtual machine image that is not using LVM to manage its " -"partitions, use the command to find an unused loop device. " -"" -msgstr "" -"パーティション管理に LVM を使用していない raw 形式の仮想マシンイメージがある" -"場合、 コマンドを使用して未使用の loop デバイスを見つけます。" -"" - -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:" -msgstr "" -"-u フラグを使用しない場合、またはファイルを編集して追加カ" -"スタマイズしたい場合、 が作成した libvirt XML ファイルを用い" -"て、 コマンドを実行できます。例:" - -msgid "" -"If you modify this example, the root partition, which is mounted on " -"/, must be the last partition on the drive so that it " -"can expand at run time to the disk size that your instance type provides. " -"Also note that bsd-cloudinit currently has a hard-" -"coded assumption that this is the second partition." -msgstr "" -"この例を変更する場合、/ にマウントされるルートパーティ" -"ションは、インスタンスタイプが提供するディスク容量へと実行時に拡張できるよ" -"う、ドライブの最後のパーティションにする必要があります。bsd-" -"cloudinit は、これが 2 番目のパーティションにあると仮定して、現" -"在ハードコードされています。" - -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 " -"that will let you view and interact with the guest's graphical console." -msgstr "" -"X11 アプリケーションを実行できるマシンに仮想マシンイメージを作成する予定なら" -"ば、最も簡単にそうする方法は、 GUI を使用することです。これ" -"は、Fedora 系と Debian 系のシステムにおいて、virt-manager " -"パッケージとしてインストールできます。この GUI は、ゲストのグラフィカルコン" -"ソールを表示および操作できる、組み込みの VNC クライアントを持ちます。" - -msgid "" -"If you use , the commands should look something like this:" -msgstr "" -" を使用する場合、このコマンドは以下のようになるでしょう。" - -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 "" -"LVM を使用している場合、新規 LVM 項目をパーティションテーブルに追加し、新規 " -"LVM 物理ボリュームを作成し、それをボリュームグループに追加し、ルートボリュー" -"ムの論理パーティションを拡張できます。" - -msgid "" -"If you use the OpenStack XenAPI driver, the Compute service automatically " -"adjusts the partition and file system for your instance on boot. Automatic " -"resize occurs if the following conditions are all true:" -msgstr "" -"OpenStack XenAPI ドライバーを使用する場合、Compute のサービスは、インスタンス" -"の起動時にパーティションとファイルシステムを自動的に調整します。以下の条件が" -"すべて満たされる場合、自動リサイズが実行されます。" - -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 "" -"このイメージの起動時に 8021q カーネルを読み込むために、イメージを編集したい場" -"合、/etc/sysconfig/modules/ ディレクトリに実行可能なスク" -"リプトを作成する必要があります。 guestfish コマンドを使用して" -"空のファイルを作成し、 コマンドを使用して編集できます。そし" -"て、 コマンドを使用して実行可能にします。以下" -"の行をファイルに追加し、保存します。続けて、実行可能にしま" -"す。" - -msgid "" -"If you wish to build your own images of Debian 7.0 (aka Wheezy, the current " -"stable release of Debian), you can use the package which is used to build " -"the official Debian images. It is named openstack-debian-images, and it provides a simple script for building them. This package is " -"available in Debian Unstable, Debian Jessie, and through the wheezy-" -"backports repositories. To produce a Wheezy image, simply run: " -"" -msgstr "" -"Debian 7.0 (つまり Wheezy、現在の Debian 安定リリース) のイメージを構築したい" -"場合、公式 Debian イメージを構築するために使用するパッケージを使用できます。" -"openstack-debian-images という名前のパッケージです。イメー" -"ジを構築するためのシンプルなスクリプトを提供します。このパッケージは、Debian " -"Unstable、Debian Jessie、wheezy バックポートリポジトリーから取得できます。以" -"下を実行して、Wheezy イメージを作成します。" - -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, and Linux, VirtualBox stores images by default in " -"the ~/VirtualBox VMs/ directory. The following example " -"creates a raw image in the current directory from a VirtualBox VDI image." -msgstr "" -"VirtualBox を使用して VDI イメージを作成した場合、VirtualBox に同梱されてい" -"る コマンドラインツールを使用して、raw 形式に変換できます。" -"Mac OS X、Linux の場合、VirtualBox はデフォルトで ~/VirtualBox VMs/" -" ディレクトリに保存します。以下の例は、VirtualBox VDI イメージか" -"ら raw イメージをカレントディレクトリに作成します。" - -msgid "" -"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " -"format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.4-x86_64-disk.img. " -msgstr "" -"お使いの環境で QEMU や KVM を使用している場合、qcow2 形式のイメージを使用する" -"ことを推奨します。執筆時点で最新の 64 ビット qcow2 イメージは cirros-0.3.4-x86_64-disk.img です。" - -msgid "" -"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " -"format. The most recent version of the 64-bit QCOW2 image for Ubuntu 14.04 " -"is trusty-server-cloudimg-amd64-disk1.img." -msgstr "" -"お使いの環境で QEMU や KVM を使用する場合、イメージを qcow2 形式で使用するこ" -"とを推奨します。最近の Ubuntu 14.04 の 64 ビット qcow2 イメージは、trusty-server-cloudimg-amd64-disk1.img。" -"" - -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 "" -"お使いのイメージがブートローダーとして grub2 を使用している場合、grub 設定" -"ファイルに設定行があります。例えば、/boot/grub/grub.cfg " -"が以下のようになっているでしょう。" - -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 "" -"LVM を用いてパーティションを管理している場合、パーティションをホストに公開す" -"るために、前の例にあるとおり losetup と kpartx を使用します。" - -msgid "Image cache management configuration options" -msgstr "イメージキャッシュ管理の設定オプション" - -msgid "Image format" -msgstr "イメージ形式" - -msgid "Image is complete" -msgstr "イメージの完成" - -msgid "Image metadata" -msgstr "イメージメタデータ" - -msgid "" -"Image metadata can help end users determine the nature of an image, and is " -"used by associated OpenStack components and drivers which interface with the " -"Image service." -msgstr "" -"イメージメタデータは、エンドユーザーがイメージの原型を判断する手助けになりま" -"す。また、Image service とやりとりする、関連する OpenStack コンポーネントやド" -"ライバーにより使用されます。" - -msgid "" -"Images are arranged by Ubuntu release, and by image release date, with " -"\"current\" being the most recent. For example, the page that contains the " -"most recently built image for Ubuntu 14.04 \"Trusty Tahr\" is http://cloud-images." -"ubuntu.com/trusty/current/. Scroll to the bottom of the page for " -"links to images that can be downloaded directly." -msgstr "" -"イメージは、Ubuntu のリリース、イメージのリリース日により配置されます。最新は" -"「current」になっています。例えば、Ubuntu 14.04 \"Trusty Tahr\" の最新イメー" -"ジのページは、http://cloud-images.ubuntu.com/trusty/current/ です。ページ" -"の最下部にスクロールすると、直接ダウンロードできるイメージへのリンクがありま" -"す。" - -msgid "" -"In FreeBSD 10.1 the command verifies SSL peers by default, " -"so you need to install the ca_root_nss package that " -"contains certificate authority root certificates and tell " -"where to find them. For FreeBSD 10.1 run these commands:" -msgstr "" -"FreeBSD 10.1 では、 コマンドがデフォルトで SSL 接続相手を検証" -"します。そのため、CA ルート証明書を含む ca_root_nss パッ" -"ケージをインストールし、その場所を に伝える必要があります。" -"FreeBSD 10.1 の場合、これらのコマンドを実行します。" - -msgid "" -"In a CentOS cloud image, the login account is centos." -msgstr "" -"CentOS クラウドイメージの場合、ログインアカウントは centos です。" - -msgid "" -"In a CirrOS image, the login account is cirros. The " -"password is cubswin:)" -msgstr "" -"CirrOS イメージでは、ログインアカウントは cirros です。パ" -"スワードは cubswin:) です。" - -msgid "In a Debian image, the login account is admin." -msgstr "" -"Debian イメージの場合、ログインアカウントは admin です。" - -msgid "" -"In a Fedora cloud image, the login account is fedora." -msgstr "" -"Fedora クラウドイメージの場合、ログインアカウントは fedora です。" - -msgid "" -"In a RHEL cloud image, the login account is cloud-user." -msgstr "" -"RHEL クラウドイメージの場合、ログインアカウントは cloud-user です。" - -msgid "" -"In addition to the ssh public key, an image might need additional " -"information from OpenStack, such as Provide user data " -"to instances, that the user submitted when requesting the image. For " -"example, you might want to set the host name of the instance when it is " -"booted. Or, you might wish to configure your image so that it executes user " -"data content as a script on boot." -msgstr "" -"イメージは、SSH 公開鍵に加えて、インスタンスに提供される" -"ユーザーデータなど、OpenStack からの追加情報を必要とするかもしれませ" -"ん。これは、イメージの起動時に、ユーザーが指定するものです。例えば、インスタ" -"ンスの起動時に、ホスト名を設定したいかもしれません。または、スクリプトのよう" -"なユーザーデータの内容を起動時に実行できるよう、イメージを設定したいかもしれ" -"ません。" - -msgid "" -"In an Ubuntu cloud image, the login account is ubuntu." -msgstr "" -"Ubuntu クラウドイメージでは、ログインアカウントは ubuntu " -"です。" - -msgid "" -"In general, we recommend that you disable any firewalls inside of your image " -"and use OpenStack security groups to restrict access to instances. The " -"reason is that having a firewall installed on your instance can make it more " -"difficult to troubleshoot networking issues if you cannot connect to your " -"instance." -msgstr "" -"一般的に、イメージ内のファイアウォールを無効化し、インスタンスへのアクセスを" -"制限するために OpenStack のセキュリティーグループを使用することを推奨します。" -"その理由は、インスタンスにインストールされたファイアウォールは、インスタンス" -"に接続できない場合に、ネットワークの問題のトラブルシューティングが難しくなる" -"からです。" - -msgid "" -"In the /var/log/compute/compute.log file, look for the " -"identifier:" -msgstr "" -"/var/log/compute/compute.log ファイルで識別子を検索しま" -"す。" - -msgid "" -"In the configuration options window, change the " -"following settings:" -msgstr "" -"設定オプションウィンドウで、以下の設定を変更します。" - -msgid "" -"In the example above, the guest centos-6.4 uses VNC " -"display :1, which corresponds to TCP port 5901. You should be able to connect a VNC client running on your local " -"machine to display :1 on the remote machine and step through the " -"installation process." -msgstr "" -"上の例では、ゲストの centos-6.4 が VNC ディスプレイ " -":1 を使用します。これは、TCP ポート 5901 番に対応します。ローカルマシンの VNC クライアントをリモートマシンの" -"ディスプレイ :1 に接続できます。そして、インストールプロセスを進めていきま" -"す。" - -msgid "" -"In the previous example, you paused the instance, ejected the disk, and " -"unpaused the instance. In theory, you could have ejected the disk at the " -"Installation complete screen. However, our testing " -"indicates that the Ubuntu installer locks the drive so that it cannot be " -"ejected at that point." -msgstr "" -"前の例では、インスタンスを一時停止し、ディスクを取り出し、インスタンスを再開" -"しました。理論的には、インストールの完了画面でディスクを" -"取り出すことができます。しかしながら、私たちのテストにおいて、Ubuntu インス" -"トーラーがドライブをロックして、そのときに取り出せないことを確認しています。" - -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 "" -"この場合、容量を変更したいパーティションは /dev/sda2 で" -"す。新しい qcow2 イメージを作成し、容量を変更して元の内容を新しいイメージをコ" -"ピーするために コマンドを使用します。" - -msgid "" -"In this example, /dev/loop0 is free. Associate a loop " -"device with the raw image:" -msgstr "" -"この例では、/dev/loop0 が空いています。loop デバイスを " -"raw イメージに関連付けます。" - -msgid "" -"Install cloud-init package inside the Fedora guest by " -"adding the EPEL repo:" -msgstr "" -"Fedora ゲスト内に EPEL リポジトリーを追加して、cloud-init " -"パッケージをインストールします。" - -msgid "" -"Install sudo and configure the freebsd " -"user to have passwordless access:" -msgstr "" -"sudo をインストールし、freebsd ユーザー" -"がパスワードなしでアクセスできるよう設定します。" - -msgid "Install GRUB boot loader" -msgstr "GRUB ブートローダーのインストール" - -msgid "" -"Install a cloud-init RPM, which " -"is a port of the Ubuntu cloud-init package. This is the recommended approach." -msgstr "" -"cloud-init RPM をインストールしま" -"す。これは、Ubuntu cloud-init パッケージを移植したものです。これが推奨の方法です。" - -msgid "" -"Install and run the acpid service on the guest system to " -"enable the virtual machine to reboot or shutdown an instance." -msgstr "" -"ゲストシステムに acpid サービスをインストールし、実行し" -"て、仮想マシンがインスタンスを再起動やシャットダウンできるようにします。" - -msgid "Install cloud-init" -msgstr "cloud-init のインストール" - -msgid "Install the cloud-init package:" -msgstr "cloud-init パッケージをインストールします。" - -msgid "Install the ACPI service" -msgstr "ACPI サービスのインストール" - -msgid "Introduction" -msgstr "はじめに" - -msgid "" -"Issue this command to download and install the latest bsd-" -"cloudinit package, and install the necessary prerequisites." -msgstr "" -"このコマンドを実行して、最新の bsd-cloudinit パッケージを" -"ダウンロードしてインストールします。また、必要な前提パッケージをインストール" -"します。" - -msgid "" -"KVM with virtio drivers is used as the virtualization platform because that " -"is the most widely used among OpenStack operators. If you use a different " -"platform for your cloud virtualization, use that same platform in the image " -"creation step." -msgstr "" -"virtio ドライバーありの KVM が、OpenStack 運用者の間で最も幅広く使用されてい" -"るため、これを仮想化プラットフォームとして使用します。クラウド仮想化環境に別" -"のプラットフォームを使用する場合、イメージ作成時にそのプラットフォームを使用" -"してください。" - -msgid "" -"Launch a VM on your local workstation. Use the same hypervisor, virtual " -"disk, and virtual network drivers as you use in your production environment." -msgstr "" -"手元のコンピューターで仮想マシンを起動します。本番環境で使用するものと、同じ" -"ハイパーバイザー、仮想ディスクドライバー、仮想ネットワークドライバーを使用し" -"ます。" - -msgid "Log in as administrator and start a command window." -msgstr "管理者としてログインし、コマンドウィンドウを起動します。" - -msgid "" -"Log in as root user when you boot for the first time after installation." -msgstr "インストール後の初回起動時、root ユーザーとしてログインします。" - -msgid "Log in to newly created image" -msgstr "新規作成イメージへのログイン" - -msgid "Loop devices, kpartx, network block devices" -msgstr "lopp デバイス、kpartx、ネットワークブロックデバイス" - -msgid "Make a virtual drive:" -msgstr "仮想ドライブを作成します。" - -msgid "Manage the image cache" -msgstr "イメージキャッシュの管理" - -msgid "" -"Metadata can also determine the scheduling of hosts. If the " -"option is set on an image, and Compute is configured so that the " -"ImagePropertiesFilter scheduler filter is enabled " -"(default), then the scheduler only considers compute hosts that satisfy that " -"property." -msgstr "" -"メタデータは、ホストのスケジューリングも決められます。 オプ" -"ションがイメージに設定されていて、ImagePropertiesFilter スケジューラーが有効 (デフォルト) になるよう Compute が設定されて" -"いる場合、スケジューラーはプロパティーを満たすコンピュートホストのみを考慮し" -"ます。" - -msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." -msgstr "" -"Microsoft Hyper-V は、イメージに VHD (Virtual Hard Disk) 形式を使用します。" - -msgid "Microsoft Windows images" -msgstr "Microsoft Windows イメージ" - -msgid "Minimize boot delay:" -msgstr "ブート遅延を最小化します。" - -msgid "" -"Modify /etc/rc.local to fetch desired information from " -"the metadata service, as described in the next section." -msgstr "" -"メタデータサービスから必要な情報を取得するために、次のセクションに記載されて" -"いるとおり、/etc/rc.local を編集します。" - -msgid "Modify a single file inside of an image" -msgstr "イメージ内の単一ファイルの編集" - -msgid "Modify images" -msgstr "イメージの変更" - -msgid "Modify the partition table to make it aware of the additional space:" -msgstr "追加領域を認識させるためにパーティションテーブルを変更します。" - -msgid "Mount a qcow2 image (with LVM)" -msgstr "qcow2 イメージのマウント (LVM あり)" - -msgid "Mount a qcow2 image (without LVM)" -msgstr "qcow2 イメージのマウント (LVM なし)" - -msgid "Mount a raw image (with LVM)" -msgstr "raw イメージのマウント (LVM あり)" - -msgid "Mount a raw image (without LVM)" -msgstr "raw イメージのマウント (LVM なし)" - -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 "" -"このセクションに記載されたツールを用いて、信頼されないゲストイメージをマウン" -"トすることは、セキュリティーリスクがあります。それらにアクセスする場合、必ず " -"guestfish や guestmount などの libguestfs ツール群を使用してください。詳細は " -"Daniel Berrangé 氏の A reminder why you should never mount guest disk images on " -"the host OS を参照してください。" - -msgid "" -"Navigate to the CentOS mirrors page." -msgstr "" -"CentOS ミラーページに移動します。" - -msgid "" -"Network adapter to configure: Red Hat VirtIO Ethernet Adapter" -msgstr "" -"設定するネットワークアダプター: Red Hat VirtIO Ethernet Adapter" - -msgid "" -"Next, update the grub configuration. On Debian-based operating-systems such " -"as Ubuntu, run this command:" -msgstr "" -"次に grub 設定を更新します。Ubuntu などの Debian 系のオペレーティングシステム" -"の場合、このコマンドを実行します。" - -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 "" -"次に、ファイルを削除します。 guestfish コマンドを使用できま" -"す。これは、伝統的なシェルと同じ方法で動作します。" - -msgid "" -"Next, you need to use the command to identify the LVM " -"volume groups and then to expose the volumes as devices:" -msgstr "" -"次に、LVM ボリュームグループを識別するために、 コマンドを使用" -"する必要があります。また、ボリュームをデバイスとして公開するために " -" を実行します。" - -msgid "No hard-coded MAC address information" -msgstr "MAC アドレス情報の組み込みなし" - -msgid "" -"Non-Xen with cloud-init/cloud-tools: One ext3/ext4 partition (no LVM, no /" -"boot, no swap)" -msgstr "" -"cloud-init/cloud-tools ありの非 Xen : 1 つの ext3/ext4 パーティション (LVM な" -"し、/boot なし、swap なし)" - -msgid "" -"Non-Xen without cloud-init/cloud-tools: LVM" -msgstr "" -"cloud-init/cloud-tools なしの非 Xen: " -"LVM" - -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 "" -"これでイメージを Image service にアップロードする準備ができました。もうこの仮" -"想マシンイメージを libvirt により管理する必要がありません。 " -"コマンドを使用して、libvirt に通知します。" - -msgid "" -"Now that you can upload the image to the Image service, you no longer need " -"to have this virtual machine image managed by libvirt. Use the " -" command to inform libvirt:" -msgstr "" -"これで、イメージを Image service にアップロードできます。今後は、この仮想マシ" -"ンイメージは libvirt により管理する必要がありません。 コマン" -"ドを使用して libvirt に通知します。" - -msgid "OVF" -msgstr "OVF" - -msgid "Official Debian images" -msgstr "公式 Debian イメージ" - -msgid "Official Fedora images" -msgstr "Fedora 公式イメージ" - -msgid "Official Red Hat Enterprise Linux images" -msgstr "Red Hat Enterprise Linux 公式イメージ" - -msgid "Official Ubuntu images" -msgstr "Ubuntu 公式イメージ" - -msgid "Official images from other Linux distributions" -msgstr "他の Linux ディストリビューションの公式イメージ" - -msgid "Official openSUSE and SLES images" -msgstr "openSUSE、SLES 公式イメージ" - -msgid "" -"On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this " -"command:" -msgstr "" -"RHEL、CentOS などの Fedora 系の場合、openSUSE の場合、このコマンドを実行しま" -"す。" - -msgid "" -"Once the installation is completed, the VM restarts. Define a password for " -"the administrator when prompted." -msgstr "" -"インストールが完了すると、仮想マシンが再起動します。プロンプトが表示されたと" -"き、管理者のパスワードを設定します。" - -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 "" -"仮想マシンイメージを取得すると、OpenStack Image service にアップロードする前" -"に、いくつか変更したいかもしれません。イメージを変更できる、いくつかの利用可" -"能なツールを説明しています。" - -msgid "OpenStack" -msgstr "OpenStack" - -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 "" -"OpenStack Compute は、現在 OVF パッケージをサポートしないため、OpenStack で使" -"用したい場合、OVF パッケージからイメージファイルを抽出する必要があります。" - -msgid "OpenStack Foundation" -msgstr "OpenStack Foundation" - -msgid "OpenStack Linux image requirements" -msgstr "OpenStack の Linux イメージ要件" - -msgid "OpenStack Virtual Machine Image Guide" -msgstr "OpenStack 仮想マシンイメージガイド" - -msgid "Optionally, add users." -msgstr "オプションとして、ユーザーを追加します。" - -msgid "Oz" -msgstr "Oz" - -msgid "" -"Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh " -"into the instance and perform the customizations." -msgstr "" -"Oz は libvirt を呼び出して KVM 内でイメージを起動してから、Oz はインスタンス" -"に SSH でログインし、カスタマイズを実行します。" - -msgid "Packer" -msgstr "Packer" - -msgid "" -"Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux " -"kernel version < 3.0)" -msgstr "" -"Linux カーネルの準仮想化 Xen サポート (Linux カーネルバージョン < 3.0 の " -"Xen ハイパーバイザーのみ)" - -msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" -msgstr "カーネルの準仮想化 Xen サポート (Xen ハイパーバイザーのみ)" - -msgid "Partition the disks" -msgstr "ディスクのパーティション作成" - -msgid "Point the installer to a CentOS web server" -msgstr "CentOS Web サーバーの指定" - -msgid "Power off the system:" -msgstr "システムを電源オフします。" - -msgid "" -"Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel " -"did not have support for paravirtualized Xen virtual machine instances (what " -"Xen calls DomU guests). If you are running the Xen hypervisor with " -"paravirtualization, and you want to create an image for an older Linux " -"distribution that has a pre 3.0 kernel, you must ensure that the image boots " -"a kernel that has been compiled with Xen support." -msgstr "" -"Linux カーネル 3.0 以前は、Linux カーネルのメインラインブランチが準仮想化 " -"Xen 仮想マシンインスタンス (Xen は DomU ゲストと呼びます) をサポートしていま" -"せん。Xen を準仮想化で実行している場合、Linux カーネル 3.0 以前の古い Linux " -"ディストリビューションのイメージを作成したければ、そのイメージが Xen サポート" -"付きでコンパイルされたカーネルを起動する必要があります。" - -msgid "Process user data and other metadata (cloud-init)" -msgstr "ユーザーデータと他のメタデータの処理 (cloud-init)" - -msgid "Process user data and other metadata (cloud-init)" -msgstr "ユーザーデータと他のメタデータの処理 (cloud-init)" - -msgid "" -"Provide a host name for your image. If you use bsd-cloudinit, it overrides this value with the name provided by OpenStack " -"when an instance boots from this image." -msgstr "" -"イメージのホスト名を指定します。bsd-cloudinit を使" -"用する場合、このイメージからインスタンスを起動するとき、OpenStack により提供" -"される名前でこの名前を上書きします。" - -msgid "QCOW2 (KVM, Xen)" -msgstr "QCOW2 (KVM, Xen)" - -msgid "QED (KVM)" -msgstr "QED (KVM)" - -msgid "Rackspace Cloud Builders (multiple distros) images" -msgstr "Rackspace Cloud Builders (複数ディストリビューション) イメージ" - -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 "" -"Rackspace Cloud Builders は、さまざまなディストリビューション (Red Hat, " -"CentOS, Fedora, Ubuntu) の事前構築済みイメージを維持しています。これらのイ" -"メージへのリンクは、GitHub の rackerjoe/oz-image-build にあります。" - -msgid "Raw" -msgstr "Raw" - -msgid "Red Hat Enterprise Linux 6 KVM Guest Image" -msgstr "Red Hat Enterprise Linux 6 KVM ゲストイメージ" - -msgid "Red Hat Enterprise Linux 7 KVM Guest Image" -msgstr "Red Hat Enterprise Linux 7 KVM ゲストイメージ" - -msgid "" -"Red Hat maintains official Red Hat Enterprise Linux cloud images. A valid " -"Red Hat Enterprise Linux subscription is required to download these images." -msgstr "" -"Red Hat は公式 Red Hat Enterprise Linux クラウドイメージを管理しています。こ" -"れらのイメージをダウンロードする場合、Red Hat Enterprise Linux の有効なサブス" -"クリプションが必要になります。" - -msgid "Remaining licensing details are filled in by the template." -msgstr "Remaining licensing details are filled in by the template." - -msgid "" -"Remove the HWADDR line from /etc/sysconfig/network-scripts/ifcfg-" -"eth0 on Fedora-based images." -msgstr "" -"Fedora 系イメージにおいて /etc/sysconfig/network-scripts/ifcfg-" -"eth0 から HWADDR 行を削除します。" - -msgid "" -"Replace /etc/udev/rules.d/70-persistent-net.rules with " -"an empty file (contains network persistence rules, including MAC address)." -msgstr "" -"/etc/udev/rules.d/70-persistent-net.rules を空のファイル" -"に置き換えます。これは、MAC アドレスなどのネットワークの永続的ルールを含みま" -"す。" - -msgid "" -"Replace /lib/udev/rules.d/75-persistent-net-generator.rules with an empty file (this generates the file above)." -msgstr "" -"/lib/udev/rules.d/75-persistent-net-generator.rules を空" -"のファイルに置き換えます。これは上述のファイルを生成します。" - -msgid "Resize an image" -msgstr "イメージのリサイズ" - -msgid "Resize the root file system. For example, ." -msgstr "ルートファイルシステムをリサイズします。例えば、。" - -msgid "Resize the root volume file system." -msgstr "ルートボリュームのファイルシステムをリサイズします。" - -msgid "" -"Run the command to see a range of allowed --os-" -"variant options." -msgstr "" -" コマンドを実行し、--os-variant オプション" -"の利用できる値を確認します。" - -msgid "" -"Run the following command to convert a vmdk image file to a qcow2 image " -"file. " -msgstr "" -"以下のコマンドを実行して、vmdk イメージファイルを qcow2 イメージファイルに変" -"換します。" - -msgid "" -"Run the following command to convert a vmdk image file to a raw image file. " -"" -msgstr "" -"以下のコマンドを実行して、vmdk イメージファイルを raw イメージファイルに変換" -"します。" - -msgid "" -"Run the following commands from the host to eject the disk and reboot using " -"virsh, as root." -msgstr "" -"ホストから root として以下の virsh コマンドを実行して、ディスクを取り出し、再" -"起動します。" - -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 "" -"virsh を使用して、ディスクを取り出し、再起動するために、ホストから root とし" -"て以下のコマンドを実行します。仮想マシンマネージャーを使用している場合、以下" -"のコマンドを使用することもできますが、GUI を使用して、ディスクを切断し、手動" -"で停止および起動を実行することもできます。" - -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 "" -"ホストで root として以下のコマンドを実行して、マシンを一時停止し、ディスクを" -"取り出し、再開します。仮想マシンマネージャーを使用している場合、代わりに GUI " -"を使用することもできます。" - -msgid "" -"Run the following commands inside the CentOS guest to install the ACPI " -"service and configure it to start when the system boots:" -msgstr "" -"ACPI サービスをインストールし、システム起動時にサービスが起動するよう設定する" -"ために、以下のコマンドを CentOS ゲスト内で実行します。" - -msgid "" -"Run the following commands inside the Fedora guest to install the ACPI " -"service and configure it to start when the system boots:" -msgstr "" -"Fedora ゲスト内で以下のコマンドを実行して、ACPI サービスをインストールし、シ" -"ステム起動時に" - -msgid "Run the installer:" -msgstr "インストーラーを実行します。" - -msgid "SSH server running" -msgstr "SSH サーバーの実行" - -msgid "SUSE Studio" -msgstr "SUSE Studio" - -msgid "" -"SUSE provides images for openSUSE. For SUSE Linux Enterprise " -"Server (SLES), custom images can be built with a web-based tool called SUSE Studio. SUSE Studio can " -"also be used to build custom openSUSE images." -msgstr "" -"SUSE は openSUSE のイメージを提供します。SUSE Linux Enterprise " -"Server (SLES) の場合、カスタムイメージを SUSE Studio という Web ベースのツールで構築できます。" -"SUSE Studio は、openSUSE のカスタムイメージを構築するためにも使用できます。" - -msgid "" -"Second partition: A freebsd-ufs partition with a mount " -"point of / with all remaining free space." -msgstr "" -"2 番目のパーティション: すべての残り領域を使用した / マ" -"ウントポイントを持つ freebsd-ufs パーティション。" - -msgid "" -"See CentOS " -"mirror page to get a full list of mirrors, click on the \"HTTP\" link " -"of a mirror to retrieve the web site name of a mirror." -msgstr "" -"ミラーの一覧は CentOS ミラーページを参照してください。取得したいミラー Web サイト" -"名の \"HTTP\" リンクをクリックしてください。" - -msgid "" -"Select \"Yes\" when asked about installing the GRUB boot loader to the " -"master boot record." -msgstr "" -"GRUB ブートローダーをマスターブートレコードにインストールするかを確認された" -"際、「Yes」を選択します。" - -msgid "" -"Select Create to create a partition table. This " -"action is the default when no partition table exists. Then, select " -"GPT GUID Partition Table from the list. This choice is " -"the default." -msgstr "" -"パーティションテーブルを作成するために、Create を選択" -"します。この操作は、パーティションテーブルが存在しない場合のデフォルトです。" -"次に、一覧から GPT GUID Partition Table を選択します。こ" -"の選択がデフォルトです。" - -msgid "" -"Select Finish and then Commit " -"to commit your changes." -msgstr "" -"変更を反映するために、Finish を選択し、" -"Commit を選択します。" - -msgid "Select a mirror" -msgstr "ミラーの選択" - -msgid "Select a root password." -msgstr "root パスワードを選択します。" - -msgid "Select the CMOS time zone." -msgstr "CMOS のタイムゾーンを選択します。" - -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 "" -"残りのオプションは、すべてデフォルトを選択します。インストール完了時、CD-ROM " -"を取り出すようプロンプトが表示されます。" - -msgid "Select the time zone appropriate to your environment." -msgstr "環境に合わせたタイムゾーンを選択します。" - -msgid "Serial port for logging: COM1" -msgstr "ロギングするシリアルポート: COM1" - -msgid "Set the disk format for your image to one of the following values:" -msgstr "お使いのイメージのディスク形式を以下のどれかに設定します。" - -msgid "" -"Set the timezone, network configuration, installation source, and the root " -"password. Optionally, you can choose to create a user." -msgstr "" -"タイムゾーン、ネットワーク設定、インストールソース、root パスワードを設定しま" -"す。オプションとして、ユーザーを作成できます。" - -msgid "Set up disk partitioning." -msgstr "ディスクパーティションをセットアップします。" - -msgid "Set up the console:" -msgstr "コンソールをセットアップします。" - -msgid "Set up the installation destination as shown below:" -msgstr "以下に示すとおり、インストール先をセットアップします。" - -msgid "Shut down the instance" -msgstr "インスタンスのシャットダウン" - -msgid "Shut down the instance from inside the instance as a root user:" -msgstr "" -"インスタンス内から root ユーザーとしてインスタンスをシャットダウンします。" - -msgid "" -"Since January 2015, Debian provides images for direct download. They are now " -"made at the same time as the CD and DVD images of Debian. However, until " -"Debian 8.0 (aka Jessie) is out, these images are the weekly built images of " -"the testing distribution." -msgstr "" -"2015 年 1 月以降、Debian は直接ダウンロードできるイメージを提供しています。" -"今のところ、Debian の CD/DVD イメージと同時に作成されています。しかしながら、" -"Debian 8.0 (つまり Jessie) が公開されるまでは、これらのイメージが、テストディ" -"ストリビューションの週次ビルドイメージです。" - -msgid "Software selection: OpenSSH server" -msgstr "ソフトウェア選択: OpenSSH サーバー" - -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 "" -"いくつかの VNC クライアントは、 : (コロン) を ; (セミコロン) に、 _ (アンダー" -"スコア) を - (ハイフン) に置き換えます。VNC セッション経由でファイルを編集す" -"る場合、http: が http; ではないこと、authorized_keys が authorized-keys では" -"ないことを確認してください。" - -msgid "" -"Some VNC clients replace the colon (:) with a semicolon " -"(;) and the underscore (_) with a " -"hyphen (-). Make sure to specify http: " -"and not http;. Make sure to specify " -"authorized_keys and not authorized-keys." -msgstr "" -"いくつかの VNC クライアントは、コロン (:) を セミコロン " -"(;) に、アンダースコア (_) をハイフン " -"(-) に置き換えます。http; ではなく、" -"http: であること、authorized-keys では" -"なく authorized_keys であることを確認してください。" - -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 "" -"ときどき、仮想マシンイメージが最初に作成されたときに、仮想ネットワークイン" -"ターフェースカードに割り当てられた MAC アドレスの設定を削除するために、イメー" -"ジを編集する必要があります。その理由は、仮想マシンの次回起動時、MAC アドレス" -"が異なるものになるからです。この例は、/etc/udev/rules.d/70-" -"persistent-net.rules ファイルを削除し、/etc/sysconfig/" -"network-scripts/ifcfg-eth0 ファイルの HWADDR 行" -"を削除することにより、古い MAC アドレスへの参照を削除するために、guestfish を" -"使用する方法を示しています。" - -msgid "" -"Start the Windows Server 2012 installation with the command:" -msgstr "" -" コマンドを用いて Windows Server 2012 のインストールを開始し" -"ます。" - -msgid "Start the install process" -msgstr "インストールプロセスの開始" - -msgid "Start the installation process" -msgstr "インストールプロセスの開始" - -msgid "" -"Start the installation process by using either or " -" as described in the previous section. If you use " -", do not forget to connect your VNC client to the virtual " -"machine." -msgstr "" -"前のセクションに記載されている や を使用し" -"て、インストールプロセスを開始します。 を使用する場合、VNC ク" -"ライアントを仮想マシンに接続し忘れないでください。" - -msgid "" -"Start the installation process using either or " -" as described in the previous section. If you use " -", do not forget to connect your VNC client to the virtual " -"machine." -msgstr "" -"前のセクションに記載されている や を使用し" -"て、インストールプロセスを開始します。 を使用する場合、必ず " -"VNC クライアントを仮想マシンに接続してください。" - -msgid "Start the installation using as shown below:" -msgstr "" -"以下に示すとおり、 を使用してインストールを開始します。" - -msgid "Step through the install" -msgstr "インストールのステップ実行" - -msgid "" -"Step through the install, using the default options. When prompted for a " -"user name, the default (ubuntu) " -"is fine." -msgstr "" -"デフォルトのオプションを使用して、インストールを進めます。ユーザー名を聞かれ" -"た際、デフォルトの ubuntu が良い" -"でしょう。" - -msgid "Step through the installation" -msgstr "インストールのステップ実行" - -msgid "" -"Step through the installation, using the default options. The simplest thing " -"to do is to choose the \"Basic Server\" install (may be called \"Server\" " -"install on older versions of CentOS), which installs an SSH server." -msgstr "" -"デフォルトのオプションを使用して、インストールをステップ実行します。最も簡単" -"な方法は、「基本サーバー (Basic Server)」インストールを選択することです " -"(CentOS の古いバージョンでは、「サーバー (Server)」と呼んでいるかもしれませ" -"ん)。SSH サーバーがインストールされます。" - -msgid "Storage devices" -msgstr "ストレージデバイス" - -msgid "Support for snapshots." -msgstr "スナップショットをサポートしています。" - -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 "" -"「raw」イメージ形式は最もシンプルな形式です。KVM と Xen が元々サポートしてい" -"ます。raw イメージは、ブロックデバイスファイル (/dev/sda など) を コマンドでコピーして作成したファイルと" -"ビット等価であると考えられます。" - -msgid "" -"The AMI/AKI/ARI format was the initial image format supported " -"by Amazon EC2. The image consists of three files:" -msgstr "" -"AMI/AKI/ARI 形式は、Amazon EC2 によりサポートされる初期のイメー" -"ジ形式でした。このイメージは 3 種類のファイルから構成されます。" -"" - -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 "" -"qcow2 " -"(QEMU copy-on-write version 2) 形式は、KVM ハイパーバイザーで一般的に使用され" -"ます。raw 形式に加えて、以下のような追加機能があります。 " - -msgid "" -"The libguestfs project " -"has a number of other useful tools, including:" -msgstr "" -"libguestfs プロジェクト" -"は、他にも以下のような有用なツールを作成しています。" - -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 "" -"ISO 形式は、CD や DVD に一般的に使用されている、読み込" -"み専用の ISO 9660 (ECMA-119 としても知られている) ファイルシステムでフォー" -"マットしたディスクイメージです。通常は、仮想マシンイメージ形式として ISO は考" -"慮しませんが、ISO がインストール済みオペレーティングシステムを持つブート可能" -"なファイルシステムを含むため、他の仮想マシンイメージファイルと同じように取り" -"扱えます。" - -msgid "" -"The Ubuntu Server Guide has " -"documentation on how to use VMBuilder to create an Ubuntu image." -msgstr "" -"Ubuntu Server Guide には、" -"VMBuilder を使用して Ubuntu イメージを作成する方法が説明されています。" - -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 "" -"SSH に渡す -X フラグが、SSH 経由の X11 転送を有効化しま" -"す。これが動作しない場合、-Y フラグに変更してみてくださ" -"い。" - -msgid "" -"The -d3 flag tells Oz to show status information as it " -"runs." -msgstr "" -"-d3 フラグにより、Oz が実行中の状態を表示するように指定し" -"ます。" - -msgid "" -"The -f format flag is " -"optional. If omitted, will try to infer the image format." -msgstr "" -"-f format フラグはオプションで" -"す。省略すると、 はイメージ形式を判別しようとします。" - -msgid "" -"The -u tells Oz to do the customization (install extra " -"packages, run the commands) once it does the initial install." -msgstr "" -"-u により、初期インストール完了後に、Oz がカスタマイズ (追" -"加パッケージのインストール、コマンドの実行) を行うように指定します。" - -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 "" -"-x <filename> フラグにより、Oz が libvirt XML ファイ" -"ルを書き出すのに使用するファイル名を指定します (指定しない場合、デフォルトで" -"は centos64Apr_03_2013-12:39:42 のようなファイル名になり" -"ます)。" - -msgid "" -"The cloud-init package automatically fetches the public " -"key from the metadata server and places the key in an account." -msgstr "" -"cloud-init は、自動的にメタデータサーバから公開鍵を取得" -"し、アカウントに鍵を保存します。" - -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 "" -" cloud-init は、自動的にメタデータサーバーから公開鍵を取得" -"し、その鍵をアカウントに保存します。アカウントはディストリビューションにより" -"異なります。Ubuntu 系仮想マシンの場合、アカウントは ubuntu という名前です。Fedora 系仮想マシンの場合、アカウントは " -"ec2-user という名前です。" - -msgid "" -"The command can do conversion between multiple formats, " -"including qcow2, qed, raw, vdi, vhd, and vmdk." -msgstr "" -" コマンドは、複数のファイル形式間で変換できます。qcow2, qed, " -"raw, vdi, vhd, vmdk に対応しています。" - -msgid "" -"The program is a tool from the libguestfs project that allows you to modify the " -"files inside of a virtual machine image." -msgstr "" -" プログラムは、仮想マシンイメージ内のファイルを編集できる、" -"libguestfs プロジェクトの" -"ツールです。" - -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 "" -" スクリプトは、インスタンス起動時に起動し、メタデータサービス" -"プロバイダーから公開鍵を取得するために、それを検索します。公開鍵は、イメージ" -"のデフォルトユーザーアカウントに置かれます。" - -msgid "" -"The cloud-init package " -"automatically fetches the public key from the metadata server and places the " -"key in an account. You can install cloud-init inside the CentOS guest by adding the EPEL repo:" -msgstr "" -"cloud-init パッケージは、メタデー" -"タサーバーから公開鍵を自動的に取得し、その鍵をアカウントの中に置きます。EPEL " -"リポジトリーを追加することにより、CentOS ゲストの中に cloud-init をインストールできます。" - -msgid "The CentOS project maintains official images for direct download." -msgstr "" -"CentOS プロジェクトは、直接ダウンロードできる公式イメージを管理しています。" - -msgid "" -"The Fedora project maintains a list of official cloud images at . " -msgstr "" -"Fedora プロジェクトは、 に公式クラウドイメージの一覧を公開しています。" - -msgid "" -"The Image service and other OpenStack projects do not currently support the " -"container format. It is safe to specify bare as the " -"container format if you are unsure." -msgstr "" -"Image service および他の OpenStack プロジェクトは、現在コンテナー形式をサポー" -"トしません。不確かな場合、コンテナー形式として bare を指定" -"すると安全です。" - -msgid "" -"The KVM hypervisor starts the virtual machine with the libvirt name, " -"centos-6.4, with 1024MB 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 10GB 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 "" -"KVM は、libvirt 名 centos-6.4、メモリ 1024MB の仮想マシン" -"を起動します。仮想マシンは、/data/CentOS-6.4-x86_64-netinstall.iso ファイルを" -"接続した仮想 CD-ROM ドライブ、ホストの /data/centos-6.4.qcow2 に保存した " -"qcow2 形式の 10GB ハードディスクを持ちます。また、libvirt の default ネット" -"ワークを使用するよう設定します。すべてのインターフェースでリッスンしている " -"VNC サーバーがあります。libvirt は、VNC クライアントを自動的に起動しません。" -"テキストコンソールを表示しません (--no-autoconsole)。最後に、libvirt は RHEL " -"6.x ディストリビューションを実行する Linux ゲスト向けに設定を最適化しようとし" -"ます。" - -msgid "" -"The Ubuntu installer will ask how you want to manage upgrades on your " -"system. This option depends on your specific use case. If your virtual " -"machine instances will be connected to the Internet, we recommend \"Install " -"security updates automatically\"." -msgstr "" -"Ubuntu のインストーラーは、お使いのシステムのアップグレードを管理する方法を確" -"認してきます。この選択肢は具体的なユースケースにより決まります。仮想マシンイ" -"ンスタンスがインターネットに接続される場合、「Install security updates " -"automatically」(セキュリティー更新を自動的にインストール) を推奨します。" - -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 "" -"アカウントは、ディストリビューションにより異なります。Ubuntu 系の仮想マシンで" -"は、アカウントが「ubuntu」という名前です。Fedora 系の仮想マシンでは、アカウン" -"トが「ec2-user」という名前です。" - -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 "" -"アカウントはディストリビューションにより異なります。Ubuntu 系の仮想マシンの場" -"合、アカウントは ubuntu という名前です。Fedora 系の仮想マ" -"シンの場合、アカウントは ec2-user という名前です。" - -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 "" -"コンテナー形式は、仮想マシンイメージが、実際の仮想マシンに関するメタデータも" -"含むファイル形式にあるかどうかを示します。" - -msgid "" -"The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 " -"support is enabled with DHCP, which is the default." -msgstr "" -"デフォルトの TCP/IP の設定で十分です。とくに、IPv4 サポートが DHCP 付きで有効" -"化されていることを確認します。" - -msgid "The default mirror proposed by the installer should be fine." -msgstr "インストーラーにより提案されるデフォルトのミラーが良いでしょう。" - -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 "" -"仮想マシンイメージのディスク形式は、元になるディスクイメージの形式です。仮想" -"アプライアンスベンダーは、仮想マシンのディスクイメージに含める情報により、さ" -"まざまな形式を使用します。" - -msgid "" -"The disk is not detected by default by the Windows installer. When requested " -"to choose an installation target, click Load driver " -"and browse the file system to select the E:\\WIN8\\AMD64 folder. The Windows installer displays a list of drivers to " -"install. Select the VirtIO SCSI and network drivers, and continue the " -"installation." -msgstr "" -"ディスクは、デフォルトで Windows インストーラーから認識されません。インストー" -"ル先を選択する画面で、ドライバーの読み込みをクリック" -"し、ファイルシステムから E:\\WIN8\\AMD64 フォルダーを選" -"択します。Windows インストーラーは、インストールするドライバーの一覧を表示し" -"ます。VirtIO SCSI ドライバーと VirtIO ネットワークドライバーを選択し、インス" -"トールを続行します。" - -msgid "The disk on the image has only one partition." -msgstr "イメージのディスクが 1 つのパーティションを持ちます。" - -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 "" -"この類の機能をサポートする最も簡単な方法は、イメージ内に cloud-" -"init パッケージをインストールすることです。これは、デフォルトでユー" -"ザーデータを実行可能スクリプトとして取り扱い、ホスト名を設定します。" - -msgid "The file system for the image fills the original size of the image." -msgstr "イメージのファイルシステムは、イメージの元々の容量になっています。" - -msgid "The file system on the one partition is ext3 or ext4." -msgstr "1 つのパーティションのファイルシステムが ext3 または ext4 です。" - -msgid "The following command uses the minimum amount of RAM, which is 256MB:" -msgstr "以下のコマンドは、最小メモリ容量 256 MB を使用します。" - -msgid "" -"The following example shows how to use the command to " -"create an empty image file, and command to start up a " -"virtual machine using that image file. As root:" -msgstr "" -"以下の例は、 コマンドを使用して、空のイメージファイルを作成す" -"る方法、および コマンドを使用して、そのイメージファイルを用" -"いて仮想マシンを作成する方法を示します。以下を root として実行します。" - -msgid "" -"The following figure shows a completed partition table with a 1GB virtual " -"disk:" -msgstr "" -"以下の図は、1GB 仮想ディスクを持つ、完成したパーティションテーブルを示しま" -"す。" - -msgid "" -"The installer may ask you to choose a host name. The default " -"(localhost.localdomain) is fine. You install the " -"cloud-init package later, which " -"sets the host name on boot when a new instance is provisioned using this " -"image." -msgstr "" -"インストーラーが、ホスト名の入力を求めるかもしれません。デフォルトの " -"localhost.localdomain が良いでしょう。後ほど cloud-init パッケージをインストールします。こ" -"れにより、このイメージを使用して展開された新規インスタンスの起動時に、ホスト" -"名が設定されます。" - -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 "" -"インストーラーがホスト名を聞いてくるかもしれません。デフォルトの " -"ubuntu が良いでしょう。後から cloud-init パッケージをイン" -"ストールします。これは、このイメージを使用して、新しいインスタンスを展開する" -"際、ブート時にホスト名を設定します。" - -msgid "" -"The minimum supported disk size for FreeBSD is 1GB. Because the goal is to " -"make the smallest possible base image, the example uses that minimum size. " -"This size is sufficient to include the optional doc, games, and lib32 " -"collections. To include the ports collection, add another 1GB. To include " -"src, add 512MB." -msgstr "" -"FreeBSD の最小サポートディスク容量は 1GB です。目標はできる限り最小のベースイ" -"メージを作成することなので、この例は最小容量を使用します。この容量は、オプ" -"ションのドキュメント、ゲーム、lib32 コレクションを含めるには十分です。Ports " -"Collection を含める場合、さらに 1GB 必要です。ソースを含める場合、512MB 追加" -"します。" - -msgid "" -"The name of your virtual machine image is centos-6.4; you " -"need this name when you use commands to manipulate the " -"state of the image." -msgstr "" -"仮想マシンイメージの名前は centos-6.4 です。 " -" コマンドを使用してイメージの状態を操作する際に、この名前が必" -"要になります。" - -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 "" -"オペレーティングシステムは、インストール中に仮想 Ethernet カードの MAC アドレ" -"スを /etc/sysconfig/network-scripts/ifcfg-eth0 や " -"/etc/udev/rules.d/70-persistent-net.rules などの場所に記" -"録します。しかしながら、イメージが起動するたびに、仮想 Ethernet カードの " -"MAC アドレスは別の値になります。そのため、この情報は設定ファイルから削除する" -"必要があります。" - -msgid "" -"The operating system records the MAC address of the virtual Ethernet card in " -"locations such as /etc/udev/rules.d/70-persistent-net.rules during the installation process. However, each time the image " -"boots up, the virtual Ethernet card will have a different MAC address, so " -"this information must be deleted from the configuration file." -msgstr "" -"オペレーティングシステムは、インストール中に仮想ネットワークカードの MAC アド" -"レスを /etc/udev/rules.d/70-persistent-net.rules などの" -"場所に記録します。しかしながら、イメージが起動するたびに、仮想ネットワーク" -"カードは別の MAC アドレスになります。そのため、この情報は設定ファイルから削除" -"する必要があります。" - -msgid "" -"The partition table for the image describes the original size of the image." -msgstr "" -"イメージのパーティションテーブルは、イメージの元々の容量を記載しています。" - -msgid "" -"The previous script only gets the ssh public key from the metadata server. " -"It does not get user data, which is optional data that can be passed by the " -"user when requesting a new instance. User data is often used to run a custom " -"script when an instance boots." -msgstr "" -"上記のスクリプトは、メタデータサーバーから SSH 公開鍵のみを取得します。新しい" -"インスタンスの要求時に、ユーザーが指定できるオプションデータである「ユーザー" -"データ」の取得を行いません。ユーザーデータは、インスタンスの起動時に、カスタ" -"ムスクリプトを実行するためにしばしば使用されます。" - -msgid "" -"The simplest way to obtain a virtual machine image that works with OpenStack " -"is to download one that someone else has already created. Most of the images " -"contain the cloud-init package to " -"support SSH key pair and user data injection. Because many of the images " -"disable SSH password authentication by default, boot the image with an " -"injected key pair. You can SSH into the instance with the private key and " -"default login account. See the OpenStack End User Guide for more information on how to " -"create and inject key pairs with OpenStack." -msgstr "" -"OpenStack で動作する仮想マシンイメージを取得する最も簡単な方法は、すでに作成" -"されたものをダウンロードすることです。ほとんどのイメージは、SSH キーペアと" -"ユーザーデータのインジェクションをサポートするために、cloud-init パッケージを含みます。多くのイメージがデ" -"フォルトで SSH パスワード認証を無効化しているため、キーペアインジェクションと" -"一緒にイメージを起動します。秘密鍵とデフォルトのログインアカウントでインスタ" -"ンスに SSH ログインできます。OpenStack でキーペアを作成して、インジェクション" -"する方法の詳細は、OpenStack エンドユーザーガイドを参照してください。" - -msgid "The simplest way to support this is to install in your image the:" -msgstr "" -"これをサポートするための最も簡単な方法は、イメージに以下をインストールするこ" -"とです。" - -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 5GB 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 10GB. When the disk for an instance is resized up, " -"zeros are just added to the end." -msgstr "" -"仮想マシンイメージのディスク容量は、イメージの初期作成時に決められます。しか" -"しながら、OpenStack により、別のフレーバーを指定して、インスタンスを別の容量" -"で起動できます。例えば、イメージが 5GB ディスクで作成し、インスタンスを m1." -"small のフレーバーで起動した場合、仮想マシンインスタンスはデフォルトで 10GB " -"の主ディスクを持ちます。インスタンスのディスクが容量拡張された場合、単に最後" -"に 0 が書き込まれます。" - -msgid "" -"The typical way that users access virtual machines running on OpenStack is " -"to ssh using public key authentication. For this to work, your virtual " -"machine image must be configured to download the ssh public key from the " -"OpenStack metadata service or config drive, at boot time." -msgstr "" -"ユーザーが OpenStack で動作する仮想マシンにアクセスする一般的な方法は、公開鍵" -"認証を使用した SSH です。このために、仮想マシンイメージは、OpenStack メタデー" -"タサービスやコンフィグドライブから SSH 公開鍵を起動時にダウンロードするよう設" -"定する必要があります。" - -msgid "" -"The underlying image file that you created with is ready to " -"be uploaded. For example, you can upload the /tmp/centos-6.4." -"qcow2 image to the Image service." -msgstr "" -" を用いて作成したベースとなるイメージファイルは、アップロード" -"できる状態になりました。例えば、/tmp/centos-6.4.qcow2 イ" -"メージを Image service にアップロードできます。" - -msgid "" -"The underlying image file that you created with , such as " -"/tmp/trusty.qcow2, is now ready for uploading to the " -"OpenStack Image service." -msgstr "" -"/tmp/trusty.qcow2 のような、 を用いて作" -"成したイメージファイルは、これで OpenStack Image service にアップロードする準" -"備ができました。" - -msgid "" -"The underlying image file that you created with qemu-img create is ready to " -"be uploaded to the Image service." -msgstr "" -"qemu-img create を用いて作成した、ベースとなるイメージを Image service にアッ" -"プロードする準備ができました。" - -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 "" -"Microsoft Server 2012 に同梱されている Hyper-V は、より新しい VHDX 形式を使用します。これは、より大きなディスク容量のサポート、電源障害時" -"のデータ破損からの保護など、VHD にはない機能がいくつかあります。" - -msgid "" -"The virtualized CMOS almost always stores its time in UTC, so unless you " -"know otherwise, select UTC." -msgstr "" -"仮想化された CMOS は、その時刻を必ず UTC で保存します。そのため、どちらかわか" -"らなければ、UTC を選択してください。" - -msgid "Then, during the boot process, you must:" -msgstr "そして、ブート中に以下を実行する必要があります。" - -msgid "" -"There are different options for partitioning the disks. The default " -"installation uses LVM partitions, and creates three partitions (/" -"boot, /, swap), which works fine. " -"Alternatively, you might want to create a single ext4 partition that is " -"mounted to \"/\", which also works fine." -msgstr "" -"ディスクのパーティションは、さまざまな選択肢があります。デフォルトでは、LVM " -"パーティションが使用され、3 つのパーティション (/boot、" -"/、swap) が作成されます。これでうまく動作します。この代" -"わりに、単一の ext4 パーティション を作成し、/ にマウント" -"したい場合もあるでしょう。これもうまく動作します。" - -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 "" -"ディスクのパーティションは、さまざまな選択肢があります。デフォルトは、うまく" -"動作する LVM パーティションを使用し、3 つのパーティション (/boot、/、swap) を作成します。この代わりに、単一の " -"ext4 パーティション を作成し、/ にマウントすることもうまく" -"動作するでしょう。" - -msgid "There are several tools that are designed to automate image creation." -msgstr "イメージ作成を自動化するために設計されたツールがいくつかあります。" - -msgid "" -"There is a known bug in Ubuntu 14.04; when you select \"Continue\", the " -"virtual machine will shut down, even though it says it will reboot." -msgstr "" -"Ubuntu 14.04 には既知のバグがあります。「続行」を選択したとき、再起動を選択し" -"ていた場合でも、仮想マシンがシャットダウンします。" - -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 "" -" というユーティリティーがあります。これは、MAC アドレス参照の" -"削除など、さまざまなクリーンアップ作業を実行します。決まった場所にある仮想マ" -"シンイメージをクリーンアップします。" - -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 "" -"guestfish には、非常にさまざまな機能がありますが、このドキュメントの範囲を超" -"えています。これらのツールを用いて実行できることは、\n" -"guestfs-" -"recipes を参照することを推奨します。" - -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 "" -"そのため、Xen を使用する場合、イメージの作成時に、(LVM により管理されていな" -"い) ext3 / ext4 パーティションを作成することを推奨します。それ以外の場合、こ" -"のまま読み進んでください。" - -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 "" -"この Oz テンプレートでは、Centos 6.4 インストール ISO のダウンロード場所を指" -"定します。Oz は、バージョン情報を使って、使用する kickstart ファイルを識別し" -"ます。この場合は、RHEL6.auto になります。リポジトリーとして " -"EPEL を追加し、このファイルの packages セクションに指定さ" -"れているepel-release、cloud-utils、" -"cloud-init パッケージをインストールします。" - -msgid "This VM must also have Internet access to download packages." -msgstr "" -"この仮想マシンは、パッケージをダウンロードするために、インターネットにアクセ" -"スできる必要があります。" - -msgid "" -"This example creates a Windows Server 2012 qcow2 image, using and the KVM hypervisor." -msgstr "" -"この例は、 と KVM ハイパーバイザーを用いて、Windows Server " -"2012 qcow2 イメージを作成します。" - -msgid "" -"This example creates a generic, bootable Ubuntu image of the latest release." -msgstr "" -"この例は、最新リリースの Ubuntu の汎用的なブート可能なイメージを作成します。" - -msgid "" -"This example creates a minimal FreeBSD image that is compatible with " -"OpenStack and bsd-cloudinit. The bsd-" -"cloudinit program is independently maintained and in active " -"development. The best source of information on the current state of the " -"project is at http://pellaeon.github.io/bsd-cloudinit/." -msgstr "" -"この例は、OpenStack と bsd-cloudinit と互換性があ" -"る、最小の FreeBSD イメージを作成します。bsd-cloudinit プログラムは、独立してメンテナンスされており、活発に開発されてい" -"ます。プロジェクトの現状に関する最良の情報源は http://pellaeon.github.io/bsd-cloudinit/" -" です。" - -msgid "" -"This example creates the image as before, but for arm architecture. More " -"elements are available in the git source directory and documented in the diskimage-builder elements " -"documentation." -msgstr "" -"この例は、前の例と同じようにイメージを作成しますが、arm アーキテクチャー向け" -"です。様々なエレメントが git ソースディレクトリー と " -"diskimage-builder のドキュメント にあります。" - -msgid "" -"This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image " -"for a different version of Ubuntu, follow these steps with the noted " -"differences." -msgstr "" -"この例は、Ubuntu 14.04 (Trusty Tahr) イメージをインストールします。別のバー" -"ジョンの Ubuntu イメージを作成する場合、注記した差分の手順を実行してくださ" -"い。" - -msgid "" -"This example shows how to create a FreeBSD 10 image. To create a FreeBSD 9.2 " -"image, follow these steps with the noted differences." -msgstr "" -"この例は、FreeBSD 10 イメージを作成する方法を示しています。FreeBSD 9.2 イメー" -"ジを作成する場合、違いを記載されたこれらの手順を実行します。" - -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 "" -"この例は、 を使用して、ファイルを編集する方法を示します。この" -"コマンドは、-a フラグの引数としてファイル名を、-" -"d フラグの引数としてドメイン名を利用できます。以下の例は、これを使" -"用して、現在動作中の libvirt ドメイン名 instance-000000e1 " -"のインスタンスにある /etc/shadow ファイルを編集する方法" -"について示します。" - -msgid "" -"This example shows you how to install a CentOS image and focuses mainly on " -"CentOS 6.4. Because the CentOS installation process might differ across " -"versions, the installation steps might differ if you use a different version " -"of CentOS." -msgstr "" -"この例は、CentOS イメージのインストール方法を説明します。おもに CentOS 6.4 を" -"対象にしています。CentOS のインストールプロセスはバージョンにより異なる可能性" -"があるため、違うバージョンの CentOS を使用している場合、インストール手順が異" -"なる可能性があります。" - -msgid "" -"This example will convert a raw image file named centos7.img to a qcow2 image file." -msgstr "" -"この例は、centos7.img という名前の raw イメージファイル" -"を qcow2 イメージファイルに変換します。" - -msgid "" -"This guide describes how to obtain, create, and modify virtual machine " -"images that are compatible with OpenStack." -msgstr "" -"このガイドは、OpenStack で利用可能な仮想マシンイメージを取得、作成、更新する" -"方法について説明します。" - -msgid "This is a virtual machine image in raw format, as described above." -msgstr "これは、上述の raw 形式の仮想マシンイメージです。" - -msgid "" -"This menu enables you to update previous settings. Check that the settings " -"are correct, and click exit." -msgstr "" -"このメニューにより、これまでの設定を更新できます。設定が正しいことを確認し" -"て、exit をクリックします。" - -msgid "" -"This sets console output to go to the serial console, which is displayed by " -", and the video console for sites with VNC or Spice " -"configured." -msgstr "" -"これは、コンソールの出力先をシリアルコンソールに設定します。 " -"により、ここに表示されます。これは、設定した VNC や SPICE を用いたサイトのビ" -"デオコンソールです。" - -msgid "" -"This starts a guestfish session. Note that the guestfish prompt looks like a " -"fish: > <fs>." -msgstr "" -"これにより guestfish セッションが始まります。guestfish プロンプトは " -"> <fs> のようになることに注意してください。" - -msgid "This will launch a VM and start the installation process." -msgstr "これにより、仮想マシンが起動され、インストールプロセスが開始します。" - -msgid "" -"To allow Cloudbase-Init to run scripts during an " -"instance boot, set the PowerShell execution policy to be unrestricted:" -msgstr "" -"インスタンスの起動時に、Cloudbase-Init がスクリプトを" -"実行できるようにするために、PowerShell の実行ポリシーを無制限に設定します。" - -msgid "To build an image, call the following script:" -msgstr "以下のスクリプトを実行し、イメージを構築します。" - -msgid "To create a FreeBSD image" -msgstr "FreeBSD イメージの作成方法" - -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 or VirtualBox), you can use that instead and " -"just convert the file to raw once you are done." -msgstr "" -"新しいイメージを作成するために、ゲストオペレーティングシステムのインストール " -"CD/DVD の ISO ファイルが必要になります。また、仮想化のツールにアクセスする必" -"要があります。このために KVM を使用できます。または、(VMware Fusion や " -"VirtualBox などの) GUI デスクトップ仮想化ツールを持っている場合、代わりにそれ" -"を使用し、完了後にファイルを raw に変更できます。" - -msgid "" -"To eject a disk by using the command, libvirt requires that " -"you attach an empty disk at the same target that the CDROM was previously " -"attached, which should be hdc. You can confirm the " -"appropriate target using the command." -msgstr "" -" コマンドを使用してディスクを取り出すためには、libvirt は、 " -"CD-ROM が前に接続されていた場所と同じ場所に、空のディスクを接続されていること" -"を期待します。この場所は、hdc でしょう。 " -"コマンドを使用して、適切な接続先を確認できます。" - -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 "" -" を使用して、ディスクを取り出すために、CD-ROM が前に接続され" -"ていた場所と同じ場所に、libvirt が空のディスクを接続する必要があります。この" -"場所は、hdc でしょう。 コマンドを使用し" -"て、適切な接続先を確認できます。" - -msgid "" -"To enable the hypervisor to reboot or shutdown an instance, you must install " -"and run the acpid service on the " -"guest system." -msgstr "" -"ハイパーバイザーがインスタンスを再起動やシャットダウンできるようにするため" -"に、ゲストシステムに acpid サービ" -"スをインストールし実行しておく必要があります。" - -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 "" -"SSH 公開鍵を取得し、root アカウントに追加するために、/etc/rc." -"local ファイルを編集し、「touch /var/lock/subsys/local」行の前に以" -"下の行を追加します。このコードは、rackerjoe oz-image-build CentOS 6 template から引用しました。" - -msgid "" -"To install the operating system, complete the following steps inside the VM:" -msgstr "" -"オペレーティングシステムをインストールするために、仮想マシン内で以下の手順を" -"すべて実行してください。" - -msgid "" -"To keep things brief, we'll sometimes use the term \"image\" instead of " -"\"virtual machine image\"." -msgstr "" -"簡単のため、「仮想マシンイメージ」の代わりに「イメージ」という言葉をときどき" -"使用します。" - -msgid "To run this:" -msgstr "以下を実行します。" - -msgid "" -"To see how the settings affect the deletion of a running instance, check the " -"directory where the images are stored:" -msgstr "" -"この設定が、稼働中のインスタンスの削除にどのような影響を与えるかを確認する場" -"合、イメージが保存されているディレクトリを確認してください。" - -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 "" -"イメージにより使用されるメタデータのソースを設定するために、cloud-" -"init パッケージに対して コマンドを実行します。プロ" -"ンプトの表示時、EC2 データソースを選択します。" - -msgid "" -"To verify that the libvirt \"default\" network is enabled, use the " -" command and verify that the \"default\" network is active:" -msgstr "" -"libvirt の「default」ネットワークが有効化されていることを確認するために、" -" コマンドを使用して、「default」ネットワークが有効であること" -"を確認します。" - -msgid "Tool support for image creation" -msgstr "イメージ作成のサポートツール" - -msgid "UEC tarball" -msgstr "UEC tar ファイル" - -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 "" -"Ubuntu Enterprise Cloud は、廃止された Eucalyptus ベースの Ubuntu クラウドソ" -"リューションのことです。OpenStack ベースの Ubuntu Cloud Infrastructure により" -"置き換えられました。" - -msgid "" -"Undefine the domain since you no longer need to have this virtual machine " -"image managed by libvirt:" -msgstr "" -"この仮想マシンイメージを libvirt により管理する必要がなくなったので、ドメイン" -"の定義を削除します。" - -msgid "Undefine the libvirt domain" -msgstr "libvirt ドメインの定義削除" - -msgid "Use cloud-init to fetch the public key" -msgstr "公開鍵の取得のための cloud-init の使用" - -msgid "" -"Use or to connect to the VM and start the " -"Windows installation." -msgstr "" -" または を使用して、仮想マシンに接続し、" -"Windows のインストールを" - -msgid "Use cloud-init to fetch the public key" -msgstr "cloud-init を使用した公開鍵の取得" - -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 "" -"nova.conf にあるオプションを使用して、未使用のイメージ" -"を /var/lib/nova/instances/_base/ に保存するかどうか、ど" -"の期間保存するかを制御します。インスタンスのライブマイグレーションを設定した" -"場合、すべてのコンピュートノードは 1 つの /var/lib/nova/instances/" -" ディレクトリを共有します。" - -msgid "" -"Use the virt-sysprep utility. This performs various " -"cleanup tasks such as removing the MAC address references. It will clean up " -"a virtual machine image in place:" -msgstr "" -"virt-sysprep ユーティリティーを使用します。これは、MAC ア" -"ドレスの参照など、さまざまなクリーンアップ作業を実行します。仮想マシンイメー" -"ジが正しい場所にクリーンアップされます。" - -msgid "Use the command to get the VNC port number." -msgstr " コマンドを使用して、VNC ポート番号を取得します。" - -msgid "Use the virt-manager X11 GUI" -msgstr "仮想マシンマネージャー X11 GUI の使用" - -msgid "Use virt-install and connect by using a local VNC client" -msgstr "virt-install の使用とローカル VNC クライアントを用いた接続" - -msgid "Username: Administrator" -msgstr "ユーザー名: Administrator" - -msgid "Using sparse representation, so the image size is smaller." -msgstr "スパースな形式を使用するため、イメージ容量が小さいです。" - -msgid "VBoxManage: VDI (VirtualBox) to raw" -msgstr "VBoxManage: VDI (VirtualBox) から raw へ" - -msgid "VDI" -msgstr "VDI" - -msgid "VDI (VirtualBox)" -msgstr "VDI (VirtualBox)" - -msgid "VHD" -msgstr "VHD" - -msgid "VHD (Hyper-V)" -msgstr "VHD (Hyper-V)" - -msgid "VHDX" -msgstr "VHDX" - -msgid "VM Image Guide" -msgstr "仮想マシンイメージガイド" - -msgid "VMBuilder" -msgstr "VMBuilder" - -msgid "VMDK" -msgstr "VMDK" - -msgid "VMDK (VMware)" -msgstr "VMDK (VMware)" - -msgid "" -"VMware's ESXi hypervisor uses the VMDK (Virtual Machine " -"Disk) format for images." -msgstr "" -"VMware の ESXi ハイパーバイザーは、イメージに VMDK (Virtual " -"Machine Disk) 形式を使用します。" - -msgid "VeeWee" -msgstr "VeeWee" - -msgid "Verify the libvirt default network is running" -msgstr "libvirt default ネットワークの動作確認" - -msgid "" -"Virtual machine images come in different formats, some of which are " -"described below." -msgstr "" -"仮想マシンイメージには、さまざまな形式があります。いくつかを以下に記載しま" -"す。" - -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 "" -"VirtualBox は、イメージファイルに VDI (Virtual Disk Image) 形式を" -"使用します。OpenStack Compute のハイパーバイザーは、VDI をサポートしないた" -"め、これらのファイルを OpenStack で使用するために、別の形式に変換する必要があ" -"ります。" - -msgid "Volume-from-Image properties" -msgstr "Volume-from-Image プロパティ" - -msgid "Wait for the machine shutdown." -msgstr "マシンがシャットダウンされるのを待ちます。" - -msgid "" -"We don't recommend creating raw images by dd'ing block device files, we " -"discuss how to create raw images later." -msgstr "" -"ブロックデバイスファイルを dd して、raw イメージを作成することは推奨しませ" -"ん。後ほど raw イメージを作成する方法については説明します。" - -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 "" -"何かしらの処理を実行する前に、まず guestfish プロンプトで コ" -"マンドを実行する必要があります。これにより、すべてのファイル操作を実行するた" -"めに使用する、仮想マシンが起動します。これで、 コマンドを使用して、イメージにあるファイルシステムを表示できます。" -"ルートパーティションを含む、論理ボリュームをマウントする必要" -"があります。" - -msgid "" -"We're done, so we can exit using the command:" -msgstr "" -"これで完了したので、 コマンドを用いて終了できます。" -"" - -msgid "Web site name: mirror.umd.edu" -msgstr "Web サイト名: mirror.umd.edu" - -msgid "What is a virtual machine image?" -msgstr "仮想マシンイメージとは何でしょうか?" - -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 "" -"Ubuntu イメージの構築時、 が使用するメタデータのソースを明示" -"的に設定する必要があります。OpenStack メタデータサーバーは、Amazon EC2 のイ" -"メージにより使用される EC2 メタデータサービスを真似ています。" - -msgid "" -"When converting an image file with Windows OS, ensure the virtio driver is " -"installed. Otherwise, you will get a blue screen of death or BSOD when " -"launching the image due to lack of the virtio driver. Another option is to " -"set the image properties as below when you update the image in glance to " -"avoid this issue, but it will reduce performance significantly." -msgstr "" -"Windows OS のイメージファイルを変換するとき、virtio ドライバーがインストール" -"されていることを確認してください。そうでなければ、イメージの起動時に、virtio " -"ドライバー不足により、ブルースクリーンで停止するでしょう。別の方法として、こ" -"の問題を避けるために glance にあるイメージを更新するときに、イメージのプロパ" -"ティーを設定することです。しかし、これは大幅に性能が悪くなります。" - -msgid "" -"When creating Block Storage volumes from images, also consider your " -"configured image properties. If you alter the core image properties, you " -"should also update your Block Storage configuration. Amend " -"in the /etc/cinder/cinder.conf file on all controller " -"nodes to match the core properties you have set in the Image service." -msgstr "" -"Block Storage のボリュームをイメージから作成した場合、イメージのプロパティを" -"設定することを考慮します。イメージの主要プロパティを変更する場合、Block " -"Storage の設定も更新すべきです。すべてのコントローラーノードで /" -"etc/cinder/cinder.conf ファイルの を修正して、" -"Image Service に設定した主要プロパティを一致させます。" - -msgid "" -"When prompted about the optional doc, games, lib32, ports, and " -"src system components, select only those that you need. " -"It is possible to have a fully functional installation without selecting " -"additional components selected. As noted previously, a minimal system with a " -"1GB virtual disk supports doc, games, and lib32 inclusive. The ports " -"collection requires at least 1GB additional space and possibly more if you " -"plan to install many ports. The src collection requires an additional 512MB." -msgstr "" -"オプションのシステムコンポーネント doc、games、lib32、ports、src に関するプロンプトが表示されたとき、必要なもののみを選択します。追加" -"コンポーネントを選択しなくても、完全に動作するインストールを実行できます。前" -"に記載したとおり、1 GB 仮想ディスクを持つシステムは、doc、games、lib32 を含め" -"られます。ports コレクションは、少なくとも 1GB の追加領域が必要です。多くの " -"ports をインストールする予定がある場合、さらに多くなるかもしれません。src コ" -"レクションは、512MB の追加が必要です。" - -msgid "" -"When prompted, choose to run the ISO in Install mode." -msgstr "" -"プロンプト表示時、Install モードで ISO の実行を選択し" -"ます。" - -msgid "" -"When the installation has completed, the Congratulations, your " -"CentOS installation is complete screen appears." -msgstr "" -"インストールが完了すると、Congratulations, your CentOS " -"installation is complete 画面が表示されます。" - -msgid "" -"When the installation is done, in the Complete the Cloudbase-Init " -"Setup Wizard window, select the Run Sysprep " -"and Shutdown check boxes and click Finish." -msgstr "" -"インストール完了後、Complete the Cloudbase-Init Setup Wizard ウィンドウで、Run Sysprep と " -"Shutdown のチェックボックスを選択し、Finish をクリックします。" - -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 "" -"qcow2 形式のイメージを使用している場合、「customize before install」オプショ" -"ンをチェックし、ディスクのプロパティから明示的に qcow2 形式を選択すべきです。" -"これにより、仮想マシンのディスク容量が正しくなります。" - -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 "" -"libvirt default ネットワークの利用時、libvirt が仮想マシン" -"のインターフェースを virbr0 という名前のブリッジに接続しま" -"す。libvirt により管理される dnsmasq プロセスが動作しています。" -"192.168.122.0/24 サブネットに IP アドレスを払い出します。また、libvirt がこの" -"サブネットに IP アドレスを NAT する iptables ルールを作成します。" - -msgid "" -"When you add an image to the Image service, you can specify its disk and " -"container formats." -msgstr "" -"イメージを Image に追加するとき、そのディスクとコンテナー形式を指定できます。" - -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 "" -"インストール後に初めて起動するとき、認証ツールに関するプロンプトが表示される" -"かもしれませんが、そのまま「Exit」を選択します。そして、指定した root のパス" -"ワードを使用して、root としてログインします。" - -msgid "" -"When you boot for the first time after installation, you might be prompted " -"about authentication tools. Select Exit. Then, log in " -"as root." -msgstr "" -"インストール後、初めて起動する場合、認証ツールに関するプロンプトが表示されま" -"す。Exit を選択します。そして、root としてログインしま" -"す。" - -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 "" -"Linux イメージの作成時、ディスクをパーティション化する方法を決める必要があり" -"ます。パーティション方法の選択により、以下のセクションに記載されているとお" -"り、リサイズ機能に影響を与える可能性があります。" - -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 "" -"新しい仮想マシンイメージの作成時、ハイパーバイザーのグラフィカルコンソールに" -"接続する必要があります。これは、仮想マシンのディスプレイとして機能し、お使い" -"のキーボードとマウスを使用して、ゲストオペレーティングシステムのインストー" -"ラーを操作できます。KVM は、VNC (Virtual Network Computing) プロトコ" -"ル、より新しい SPICE プロ" -"トコルを使用して、グラフィカルコンソールを利用できます。ここでは、お使いのデ" -"スクトップで動作する VNC クライアントを見つけやすいので、VNC プロトコルを使用" -"します。" - -msgid "When you're done, clean up:" -msgstr "完了後、クリーンアップします。" - -msgid "When you're done, clean up:" -msgstr "完了後、クリーンアップします。" - -msgid "" -"With these packages installed, the image performs the root partition resize " -"on boot. For example, in the /etc/rc.local file. These " -"packages are in the Ubuntu and Debian package repository, as well as the " -"EPEL repository (for Fedora/RHEL/CentOS/Scientific Linux guests)." -msgstr "" -"これらのパッケージをインストールすると、このイメージは、起動時にルートパー" -"ティションの容量変更を実行できるようになります。例えば、/etc/rc." -"local にあります。これらのパッケージは、Ubuntu や Debian のパッ" -"ケージリポジトリーにあります。また、Fedora、RHEL、CentOS、Scientific Linux の" -"ゲストの場合、EPEL リポジトリーにあります。" - -msgid "Write a custom script to fetch the public key" -msgstr "公開鍵の取得のためのカスタムスクリプトの書き込み" - -msgid "Write a script to fetch the public key (if no cloud-init)" -msgstr "公開鍵取得のスクリプトの書き込み (cloud-init なしの場合)" - -msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" -msgstr "Xen: 1 ext3/ext4 パーティション (LVM なし、/boot なし、swap なし)" - -msgid "" -"You can access this information through the metadata service or referring to " -"Store metadata on the configuration drive. As the OpenStack " -"metadata service is compatible with version 2009-04-04 of the Amazon EC2 " -"metadata service, consult the Amazon EC2 documentation on Using Instance Metadata for details on " -"how to retrieve user data." -msgstr "" -"メタデータサービス、または、コンフィグドライブへのメタデータの保存により、この情報にアクセスできます。OpenStack メタデータサービスは、" -"Amazon EC2 メタデータサービスの 2009-04-04 版と互換性があるので、ユーザーデー" -"タの取得に関する詳細は、Using Instance " -"Metadata にある Amazon EC2 ドキュメントを参照してください。" - -msgid "" -"You can add metadata to Image service images by using the --" -"property key=value parameter with the or command. " -"More than one property can be specified. For example:" -msgstr "" -" や コマンドに --property " -"key=value " -"パラメーターを使用することにより、Image service のイメージにメタデータを追加" -"できます。複数のプロパティを指定できます。例:" - -msgid "" -"You can also use the GUI to detach and reboot it by manually stopping and " -"starting." -msgstr "" -"GUI を使用して、切断し、手動で停止して起動することにより再起動することもでき" -"ます。" - -msgid "" -"You can change the name of the account used by cloud-init " -"by editing the /etc/cloud/cloud.cfg file and adding a " -"line with a different user. For example, to configure cloud-init to put the key in an account named admin, add this line to the " -"configuration file:" -msgstr "" -"/etc/cloud/cloud.cfg ファイルを編集し、別のユーザーの行" -"を追加することにより、cloud-init により使用されるアカウン" -"ト名を変更できます。例えば、cloud-init が admin という名前" -"のアカウントに鍵を追加するよう設定するために、以下の行を設定ファイルに追加し" -"ます。" - -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 "" -"/etc/cloud/cloud.cfg ファイルを編集し、別のユーザーの行" -"を追加することにより、cloud-init により使用されるアカウン" -"ト名を変更できます。例えば、cloud-init を編集して、" -"admin という名前のアカウントに鍵を置くために、以下の行を含" -"むように設定ファイルを編集します。" - -msgid "" -"You can change the name of the account used by cloud-init by editing the /etc/cloud/cloud.cfg file and adding a line with a different user. For example, to " -"configure cloud-init to put the " -"key in an account named admin, add this line to the " -"configuration file:" -msgstr "" -"cloud-init により使用されるアカウ" -"ント名を変更できます。/etc/cloud/cloud.cfg ファイルを編" -"集し、別のユーザーの行を追加します。例えば、admin という名" -"前のアカウントに鍵を置くように、cloud-init を設定する場合、設定ファイルに以下の行を追加します。" - -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 "" -"/etc/cloud/cloud.cfg ファイルを編集し、別のユーザー名を" -"書いた行を追加して、cloud-init により使用されるアカウント名を変更できます。例" -"えば、「admin」という名前のアカウントに SSH 鍵を置くよう cloud-init を設定す" -"る場合、次の行のように設定ファイルを編集します。" - -msgid "" -"You can set the container format for your image to one of the following " -"values:" -msgstr "イメージのコンテナー形式に以下のどれかを設定できます。" - -msgid "" -"You can specify up to 1GB additional RAM to make the installation process " -"run faster." -msgstr "" -"インストールプロセスを高速化するために、メモリを最大で 1GB まで指定できます。" - -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 "" -"お使いのイメージが、/boot が LVM により管理されていない" -"という要件がある古い Linux ディストリビューションでなければ、/" -"boot パーティションは必要ありません。" - -msgid "" -"You do not need to add users at this time. The bsd-cloudinit program adds a freebsd user account if one " -"does not exist. The ssh keys for " -"this user are associated with OpenStack. To customize this user account, you " -"can create it now. For example, you might want to customize the shell for " -"the user." -msgstr "" -"このとき、ユーザーを追加する必要がありません。bsd-cloudinit プログラムは、freebsd ユーザーアカウントが存" -"在しない場合、それを追加します。このユーザーアカウント用の ssh 鍵が OpenStack を用いて関連付けられます。この" -"ユーザーアカウントをカスタマイズする場合、いま作成します。例えば、ユーザーの" -"シェルをカスタマイズしたい場合です。" - -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 "" -"カーネルがブートログを ttyS0 デバイスに書き込めるよう、イ" -"メージを設定する必要があります。とくに、ブート時に console=ttyS0 引数をカーネルに渡す必要があります。" - -msgid "You must configure these items for your image:" -msgstr "イメージのこれらの項目を設定する必要があります。" - -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 "" -"イメージの中に SSH サーバーをインストールし、起動時に開始するよう設定する必要" -"があります。そうでなければ、OpenStack 内に起動したインスタンスに SSH 接続でき" -"ません。このパッケージは、一般的に openssh-server という名" -"前です。" - -msgid "" -"You must remove the network persistence rules in the image because they " -"cause the network interface in the instance to come up as an interface other " -"than eth0. This is because your image has a record of the MAC address of the " -"network interface card when it was first installed, and this MAC address is " -"different each time the instance boots. You should alter the following files:" -msgstr "" -"ネットワーク永続化ルールにより、インスタンスのネットワークインターフェースが " -"eth0 以外のインターフェースとして起動するため、イメージでそのルールを削除する" -"必要があります。これは、最初にインストールしたときに、ネットワークインター" -"フェースカードの MAC が記録されるため、インスタンスの起動ごとに別の MAC アド" -"レスになるためです。以下のファイルを変更します。" - -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 "" -"qcow2 イメージをマウントするために、nbd (ネットワークブ" -"ロックデバイス) カーネルモジュールを読み込む必要があります。この例は、今回の" -"目的に十分である、16 個のブロックデバイスをサポートします。root として、以下" -"のとおり実行します。" - -msgid "" -"You now have a VM that boots from the downloaded install ISO and is " -"connected to the blank virtual disk that you created previously." -msgstr "" -"これで、ダウンロードしたインストール ISO から起動し、前に作成した空の仮想ディ" -"スクを接続した、仮想マシンができました。" - -msgid "" -"You saved the netinstall ISO image to the /data/isos " -"directory." -msgstr "" -"ネットワークインストール ISO イメージは /data/isos ディ" -"レクトリーに保存されています。" - -msgid "Your image is ready to upload to the Image service:" -msgstr "お使いのイメージを Image にアップロードする準備ができました。" - -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 "" -"イメージは、ユーザーにより要求された容量になるよう、起動時にパーティションを" -"リサイズできる必要があります。そうでなければ、インスタンスのディスク容量がイ" -"メージ作成時のディスク容量を超えるフレーバーと関連づけられている場合、インス" -"タンスの起動後、追加のストレージにアクセスできるよう、手動でリサイズする必要" -"があります。" - -msgid "Your script must do something like the following:" -msgstr "スクリプトは以下のようなことを実行する必要があります。" - -msgid "current" -msgstr "カレント" - -msgid "fedora-20" -msgstr "fedora-20" - -msgid "guestfish" -msgstr "guestfish" - -msgid "guestmount" -msgstr "guestmount" - -msgid "imagefactory" -msgstr "imagefactory" - -msgid "img-uuid" -msgstr "img-uuid" - -msgid "node-root" -msgstr "node-root" - -msgid "preallocate_images=none" -msgstr "preallocate_images=none" - -msgid "qcow2" -msgstr "qcow2" - -msgid "qed" -msgstr "qed" - -msgid "qemu-img convert: raw, qcow2, qed, vdi, vmdk, vhd" -msgstr "qemu-img convert: raw, qcow2, qed, vdi, vmdk, vhd" - -msgid "qemu-img format strings" -msgstr "qemu-img の形式の文字列" - -msgid "raw" -msgstr "raw" - -msgid "remove_unused_base_images=True" -msgstr "remove_unused_base_images=True" - -msgid "remove_unused_original_minimum_age_seconds=86400" -msgstr "remove_unused_original_minimum_age_seconds=86400" - -msgid "remove_unused_resized_minimum_age_seconds=3600" -msgstr "remove_unused_resized_minimum_age_seconds=3600" - -msgid "sda6" -msgstr "sda6" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -msgid "translator-credits" -msgstr "Tomoyuki KATO , 2013-2015" - -msgid "vdi" -msgstr "vdi" - -msgid "vg00" -msgstr "vg00" - -msgid "virt-* tools" -msgstr "virt-* ツール" - -msgid "vm-image" -msgstr "vm-image" - -msgid "vm-name" -msgstr "vm-name" - -msgid "vmdk" -msgstr "vmdk" - -msgid "vpc" -msgstr "vpc" diff --git a/doc/image-guide/locale/zh_CN.po b/doc/image-guide/locale/zh_CN.po deleted file mode 100644 index 218e41f128..0000000000 --- a/doc/image-guide/locale/zh_CN.po +++ /dev/null @@ -1,3685 +0,0 @@ -# Translators: -# Alfred , 2015 -# blkart , 2015 -# johnwoo_lee , 2015 -# 秋林 , 2015 -# -# -# OpenStack Infra , 2015. #zanata -# actionchen , 2015. #zanata -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-23 17:24+0000\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-10-24 04:14+0000\n" -"Last-Translator: actionchen \n" -"Language: zh-CN\n" -"Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Zanata 3.7.1\n" -"Language-Team: Chinese (China)\n" - -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 "" -"（布尔型）未使用的基础镜像是否被删除？ 当设置为 True 的时候，删除未使用的基础" -"镜像的时间间隔在下面两个参数设置。如果设置为 False，基础镜像将一直不被删除。" - -msgid "" -"(IntOpt) Unused resized base images younger than this are not removed. " -"Default is 3600 seconds, or one hour." -msgstr "" -"（整数型）未使用且大小改变了的基础镜像镜像文件，低于这个值的不删除。默认是" -"3600秒，或1小时。" - -msgid "" -"(IntOpt) Unused unresized base images younger than this are not removed. " -"Default is 86400 seconds, or 24 hours." -msgstr "" -"（整数型），未使用以及未修改大小的镜像，低于这个值，不删除。默认是86400秒，或" -"24小时。" - -msgid "(StrOpt) VM image preallocation mode:" -msgstr "（字符串型）虚拟机镜像预分配模式：" - -msgid "(Type) Description" -msgstr "(类型) 描述" - -msgid "..." -msgstr "..." - -msgid "2013" -msgstr "2013" - -msgid "2014" -msgstr "2014" - -msgid "2015" -msgstr "2015" - -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 "" -"OVF (Open Virtualization Format)是一" -"种虚拟机打包格式，由 DMTF （分布式任务管理）标准组定义，单个 OVF 包包含一个或" -"多个镜像文件， .ovf 后缀的 XML元数据文件包含了关于虚拟机信息及其他文件的信" -"息。" - -msgid "" -"Diskimage-builder is an automated disk image creation tool that " -"supports a variety of distributions and architectures. Diskimage-builder " -"(DIB) can build images for Fedora, Red Hat Enterprise Linux, Ubuntu, Debian, " -"CentOS, and openSUSE. DIB is organized in a series of elements that build on " -"top of each other to create specific images." -msgstr "" -" " -"镜像生成器 是一个支持不同发行版以及体系架构的自动化磁盘镜像创建工具。" -"镜像生成器（DIB）能为 Fedora, Red Hat Enterprise Linux, Ubuntu, Debian, " -"CentOS, and openSUSE 生成镜像，DIB 是被组合一系列的工具之上的创建特殊镜像的基" -"础。" - -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 "" -"imagefactory 是一个设计为自动" -"化创建，转换以及上传镜像到不同云提供商的较新的工具。他使用 Oz 做为后端，并支" -"持包含基于 OpenStack 的云。" - -msgid "" -"virt-df for " -"displaying free space inside of an image." -msgstr "" -"virt-df 用于" -"显示镜像内的空闲空间。" - -msgid "" -"virt-edit " -"for editing a file inside of an image." -msgstr "" -"virt-edit " -"用于编辑镜像内的文件。" - -msgid "" -"virt-resize for resizing an image." -msgstr "" -"virt-resize 用于伸缩镜像文件大小。" - -msgid "" -"virt-" -"sparsify for making an image sparse." -msgstr "" -"virt-" -"sparsify 用于使镜像文件稀疏化。" - -msgid "" -"virt-sysprep for preparing an image for distribution (for example, delete SSH host " -"keys, remove MAC address info, or remove user accounts)." -msgstr "" -"virt-sysprep 用于做镜像分发前的准备工作（例如，删除SSH 主机秘钥，删除MAC地址信息，或" -"者删除用户账号）。" - -msgid "" -"virt-p2v for " -"converting a physical machine to an image that runs on KVM." -msgstr "" -"virt-p2v 用于转换" -"物理机系统到一个运行在KVM上的镜像文件。" - -msgid "" -"virt-v2v for " -"converting Xen and VMware images to KVM images." -msgstr "" -"virt-v2v 用于转" -"换 Xen 和 VMware 镜像到 KVM 镜像。" - -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 "" -"SUSE Studio 是创建和测试软" -"件程序的基于浏览器的 web 程序。他支持创建物理，虚拟或者基于云端的应用程序，并" -"且支持使用SUSE Linux Enterprise and openSUSE 发行版为基于 Openstack 的云创建" -"镜像。" - -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 "" -"Oz 是一个" -"自动化创建镜像文件的命令行工具。它是一个和 KVM 进行交互完成整个虚拟机镜像安装" -"过程的 Python 程序。它使用操作系统支持的一系列预定义的 kickstart (红帽系)文件" -"或 preseed 文件 （Debian 系），并且他也用于创建微软 Windows 镜像。在 Fedora " -"上,使用 yum 安装 Oz:" - -msgid "" -" VeeWee is " -"often used to build Vagrant " -"boxes, but it can also be used to build KVM images." -msgstr "" -" VeeWee 通常" -"用于创建 Vagrant boxses，但" -"它也可用于创建 KVM 镜像。" - -msgid "" -"cloud-init " -"package." -msgstr "" -"cloud-init 软件" -"包。" - -msgid "" -"cloud-" -"initramfs-growroot package for Ubuntu, Debian and Fedora, which " -"supports resizing root partition on the first boot." -msgstr "" -"cloud-" -"initramfs-growroot 包在 Ubuntu ， Ubuntu 和 Fedora 上支持系统首次启动" -"时改变根分区大小。" - -msgid "" -"cloud-utils " -"package, which contains the tool for extending partitions." -msgstr "" -"cloud-utils " -"包，包含了 工具来扩展分区。" - -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 "" -"VMBuilder (虚拟机" -"生成器) 是一个可为不同 hypervisors 生成虚拟机镜像的命令行工具。Ubuntu 带的 " -"VMBuilder 版本只能创建 Ubuntu 虚拟机。 Debian 带的 VMBuilder 版本能创建 " -"Ubuntu 以及 Debian 虚拟机。" - -msgid "" -" Packer is a tool for creating " -"machine images for multiple platforms from a single source configuration." -msgstr "" -" Packer 是使用单一源配置生成不" -"同平台虚拟机镜像的工具。" - -msgid "aki. An Amazon kernel image." -msgstr "aki. Amazon 内核镜像。" - -msgid "aki: An Amazon kernel image." -msgstr "aki： Amazon 内核镜像。" - -msgid "ami. An Amazon machine image." -msgstr "ami. Amazon 虚机镜像。" - -msgid "ami: An Amazon machine image." -msgstr "ami： Amazon 虚机镜像。" - -msgid "ari. An Amazon ramdisk image." -msgstr "ari. Amazon ramdisk 镜像。" - -msgid "ari: An Amazon ramdisk image." -msgstr "ari.：Amazon ramdisk 镜像。" - -msgid "" -"auto_disk_config=True is set as a property on the image " -"in the image registry." -msgstr "在镜像的属性设置了 auto_disk_config=True 。" - -msgid "" -"bare. The image does not have a container or metadata " -"envelope." -msgstr "bare. 镜像没有容器或者没有封装metadata数据。" - -msgid "" -"iso: An archive format for the data contents of an " -"optical disc, such as CD-ROM." -msgstr "iso：光盘数据内容的归档格式，例如CD-ROM。" - -msgid "none. No storage provisioning occurs up front." -msgstr "none。不分配存储。" - -msgid "ovf. The OVF container format." -msgstr "ovf. OVF容器格式。" - -msgid "" -"qcow2: Supported by the QEMU emulator that can expand " -"dynamically and supports Copy on Write." -msgstr "" -"qcow2： 由 QEMU 模拟器支持，能动态扩展以及支持写时复制特" -"性。" - -msgid "" -"raw: An unstructured disk image format; if you have a " -"file without an extension it is possibly a raw format." -msgstr "" -"raw： 无结构的磁盘镜像格式；如果你有一个无扩展名的磁盘文" -"件，那么这个磁盘文件可能是裸格式。" - -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 "" -"space。虚拟机启动时存储完全分配。$instance_dir/目录在空间足够的情况下立即 fallocate分配。并且" -"为了增加虚拟机 I/O 性能，会选择更适合的的块设备。" - -msgid "" -"vdi: Supported by VirtualBox virtual machine monitor and " -"the QEMU emulator." -msgstr "" -"vdi.：能被 VirtualBox 虚机管理程序和 QEMU 模拟器支持的格" -"式。" - -msgid "" -"vhd: The VHD disk format, a common disk format used by " -"virtual machine monitors from VMware, Xen, Microsoft, VirtualBox, and others." -msgstr "" -"vhd： VHD磁盘格式，一种被VMware, Xen, Microsoft, " -"VirtualBox, 以及其他虚拟机管理程序通用的磁盘格式。" - -msgid "" -"vmdk: Common disk format supported by many common virtual " -"machine monitors." -msgstr "vmdk.：能被多钟虚拟机管理程序支持的通用格式。" - -msgid "" -"cloud-initramfs-growroot package for Centos and RHEL." -msgstr "Centos 和 RHEL 上使用cloud-initramfs-growroot" - -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 "" -"并不直接mount镜像文件到本地文件系统，而是提供一个shell接口，" -"你可以通过这个shell接口对镜像内文件做查看，编辑，删除操作，诸如 " -", , 和 的 " -"命令，就像普通bash命令一样。" - -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 "" -"我们想编辑 ifcfg-eth0 文件以便删除 " -"HWADDR 这一行。命令将文件拷贝文件到主机，" -"调用编辑器打开文件，编辑完后将它又拷贝回原来的位置。" - -#. 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. -msgid "" -"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" -msgstr "" -"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" - -#. 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. -msgid "" -"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" -msgstr "" -"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" - -#. 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. -msgid "" -"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" -msgstr "" -"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" - -#. 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. -msgid "" -"@@image: 'figures/freebsd-partitions.png'; " -"md5=47dbba18dda83b095f370a71e1dc3413" -msgstr "" -"@@image: 'figures/freebsd-partitions.png'; " -"md5=47dbba18dda83b095f370a71e1dc3413" - -#. 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. -msgid "" -"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" -msgstr "" -"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" -msgstr "" -"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" -msgstr "" -"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-install.png'; md5=999f5b14528b82401dbe04dce8779f4c" -msgstr "" -"@@image: 'figures/ubuntu-install.png'; md5=999f5b14528b82401dbe04dce8779f4c" - -#. 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. -msgid "" -"@@image: 'figures/ubuntu-software-selection.png'; " -"md5=423be828f701345f7d20551a39f24271" -msgstr "" -"@@image: 'figures/ubuntu-software-selection.png'; " -"md5=423be828f701345f7d20551a39f24271" - -#. 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. -msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" -msgstr "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" - -#. 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. -msgid "" -"@@image: 'figures/virt-manager-new.png'; md5=4faa75d3058f6a332c01dc1dba9cecbc" -msgstr "" -"@@image: 'figures/virt-manager-new.png'; md5=4faa75d3058f6a332c01dc1dba9cecbc" - -msgid "" -"A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains " -"an AMI file, AKI file, and ARI file." -msgstr "UEC（Ubuntu 企业云） 文件是一个包含了 AMI AKI ARI文件的tar包压缩文件。" - -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 "" -"完整的 Oz 示例 已经超出本文档范围，但是我们提供一个示例。你可以在 GitHub " -"rackerjoe/oz-image-build/templates.查找到额外的 Oz 模板文" -"件。下面演示了使用 Oz 如何创建 CentOS 6.4 镜像。" - -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 "" -"虚拟化启动镜像时最先加载的内核文件。对 Linux 机器，对应的应该是" -"vmlinuz 文件。" - -msgid "" -"A virtual machine image is a single file which contains a virtual disk that " -"has a bootable operating system installed on it." -msgstr "" -"一个虚拟机镜像是一个文件，文件内包含了已经安装好可启动操作系统的虚拟磁盘。" - -msgid "AKI (Amazon Kernel Image)" -msgstr "AKI (亚马逊内核镜像)" - -msgid "AMI (Amazon Machine Image):" -msgstr "AMI (亚马逊虚机镜像):" - -msgid "AMI/AKI/ARI" -msgstr "AMI/AKI/ARI" - -msgid "ARI (Amazon Ramdisk Image)" -msgstr "ARI (亚马逊 Ramdisk 镜像)" - -msgid "" -"Accept the default keymap or select an appropriate mapping for your needs." -msgstr "接受默认键盘分布或者根据需要选择适当的键盘映射。" - -msgid "Accept the default network mirror." -msgstr "接受默认的网络镜像。" - -msgid "Access instance by using ssh public key (cloud-init)" -msgstr "使用 SSH 公钥（cloud-init）访问虚拟机" - -msgid "Access instance using ssh public key (cloud-init)" -msgstr "使用SSH 公钥访问虚拟机 (cloud-init)" - -msgid "" -"After Oz completes the initial OS install using the kickstart file, it " -"customizes the image with an update. It also removes any reference to the " -"eth0 device that libvirt creates while Oz does the customizing, as specified " -"in the command section of the XML file." -msgstr "" -"在 Oz 使用kickstart文件完成系统初始安装后，它通过更新镜像内容来定制镜像文件。" -"定制的过程它通过 在XML 文件中的 command 字段也删除任何关于" -"eth0设备的信息。" - -msgid "" -"After you exit, you can open a shell to complete manual configuration steps. " -"Select Yes to make a few OpenStack-specific changes:" -msgstr "" -"在退出后，你可以打开一个shell完成手工配置，选择 Yes 完" -"成一些OpenStack特定的修改：" - -msgid "" -"All associated properties for an image can be displayed using the " -" command. For example:" -msgstr "镜像的所有相关联的属性可以使用 命令显示。例如：" - -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 "" -"OVF 包可通过几种方式分发，例如，可以通过一系列分散的文件分发或者通过一个tar归" -"档文件（.ova后缀）分发。" - -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 "" -"在你拥有虚拟机镜像（也有人叫\"虚拟器件\"）之前，你的 OpenStack 计算云不太有" -"用，这个指南描述了如何获取，创建以及修改 OpenStack 兼容的虚拟机镜像。" - -msgid "" -"An instance must interact with the metadata service to perform several tasks " -"on start up. For example, the instance must get the ssh public key and run " -"the user data script. To ensure that the instance performs these tasks, use " -"one of these methods:" -msgstr "" -"虚拟机在启动的时候需要和元数据服务交互以便完成几个任务，例如，虚拟机必须获取" -"ssh公钥以及运行用户数据脚本。确保虚拟机能完成这些任务，使用以下几个方法之一：" - -msgid "" -"An optional ramdisk file mounted at boot time. For a Linux machine, this " -"would be an initrd file." -msgstr "" -"系统启动时可选的 ramdisk 文件，对 Linux 机器，对应的是 initrd 文件。" - -msgid "Argument to qemu-img" -msgstr "qemu-img 参数" - -msgid "" -"As of this writing, there are no Oz packages for Ubuntu, so you will need to " -"either install from the source or build your own .deb file." -msgstr "" -"在本文档编写时，没有针对 Ubuntu 的 Oz 安装包，因此你需要从源代码安装或者编译" -"自己的.deb文件包。" - -msgid "" -"As of this writing, we are not aware of other distributions that provide " -"images for download." -msgstr "在本文档编写时，我们并未发现其他Linux发行版提供镜像下载。" - -msgid "" -"As the OpenStack metadata service is compatible with version 2009-04-04 of " -"the Amazon EC2 metadata service, consult the Amazon EC2 documentation on " -"Using Instance Metadata " -"for details on how to get user data." -msgstr "" -"OpenStack 元数据服务兼容 亚马逊 EC2 2009-04-04 版本元数据服务，请参考亚马逊 " -"EC2 文档 使用虚机元数据获取如何获取" -"用户数据的详细信息。" - -msgid "" -"Assume that the name of your virtual machine image is ubuntu-14.04, which you need to know when you use commands to " -"manipulate the state of the image." -msgstr "" -"假设你的虚拟机名称是 trusty ，当你使用 " -"命令操作虚拟机状态的时候你需要虚拟机名称。" - -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 "" -"假设你有一个文件名为centos63_desktop.img的 CentOS qcow2 " -"格式的虚拟机镜像。用root用户挂载这个镜像为可读可写模式，如下：" - -msgid "Assume that:" -msgstr "假设：" - -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 "" -"假设第一个块设备(/dev/nbd0)当前未被占用，我们使用" -" 和 列出磁盘分区。以root用户执行：" -"" - -msgid "" -"At the initial Installer boot menu, choose the Install or upgrade " -"an existing system option. Step through the installation prompts. " -"Accept the defaults." -msgstr "" -"在最开始的安装启动菜单，选择 Install or upgrade an existing " -"system ，这事默认的。" - -msgid "" -"At the initial Installer boot menu, choose the Install " -"option. Step through the install prompts, the defaults should be fine." -msgstr "" -"在安装初始启动菜单中，选择 Install 。安装过程提示中，" -"默认的即可。" - -msgid "Automatic updates" -msgstr "自动更新" - -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 "" -"由于 remove_unused_original_minimum_age_seconds 的值默认是" -"86400秒（24小时），你可以等待这个时间间隔来查看基础镜像是否被删除，或者在 " -"nova.conf 内设置更短的时间间隔。修改 nova." -"conf 后，重启所有的 nova 服务。" - -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 "" -"由于 VNC 是一个标准协议，因此有多个可用的 VNC 规范的客户端实现，包括 TigerVNC（多平台），TightVNC （多平台），RealVNC（多平台），Chicken (Mac OS X),Krde (KDE), 以及 Vinagre (GNOME)." - -msgid "" -"Because qcow2 is sparse, qcow2 images are typically smaller than raw images. " -"Smaller images mean faster uploads, so it's often faster to convert a raw " -"image to qcow2 for uploading instead of uploading the raw file directly." -msgstr "" -"因为qcow2 镜像是稀疏的，因此，qcow2镜像通常比裸格式镜像小，更小的文件意味着上" -"传更快，因此通常转换裸格式镜像到qcow2格式上传比直接上传裸格式镜像文件更快。" - -msgid "" -"Because raw images don't support snapshots, OpenStack Compute will " -"automatically convert raw image files to qcow2 as needed." -msgstr "" -"因为裸格式镜像不支持快照，OpenStack 计算节点在需要的时候将会自动转换裸格式镜" -"像到qcow2格式。" - -msgid "" -"Because the default does not work, you must select manual partitioning. The " -"partition editor should list only one block device. If you use virtio for " -"the disk device driver, it is named vtbd0. Select this " -"device and run the command three times:" -msgstr "" -"因为默认的分区会导致bsd-cloudinit不能正常工作，你必须手工分区，分区编辑器仅列" -"出块设备，如果你使用 virtio 磁盘驱动，它名称是 vtbd0。选择" -"这个设备运行 三次：" - -msgid "" -"Because the goal is to make the smallest possible base image, this example " -"uses the network installation ISO. The Ubuntu 64-bit 14.04 network installer " -"ISO is at http://archive.ubuntu." -"com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini." -"iso." -msgstr "" -"由于我们的目标是制作一个最小化的可用基础镜像，本示例使用网络安装 ISO。" -"Ubuntu 14.04 64位版本的网络安装 ISO 位于 http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-" -"amd64/current/images/netboot/mini.iso。" - -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 "" -"在使用 libvirt 启动虚拟机前，检查它的 \"default\" 默认网络是否启动。虚拟机要" -"连接到外网，它的默认网络必须激活。启动 libvirt 默认网络将创建 linux 网桥( 通" -"常名称是virbr0 )，iptables 规则，以及dhcp服务器进程 " -"dnsmasq 。" - -msgid "" -"By using the same hypervisor, you can ensure that you emulate the same " -"devices that exist in production. However, if you use full hardware " -"virtualization instead of paravirtualization, you do not need to use the " -"same hypervisor; you must use the same type of virtualized hardware because " -"FreeBSD device names are related to their drivers. If the name of your root " -"block device or primary network interface in production differs than the " -"names used during image creation, errors can occur." -msgstr "" -"通过使用相同的虚拟化层，可以确保仿照你生产环境相同的虚拟设备，然而，如果你有" -"硬件虚拟化代替半虚拟化，可以不需要相同的虚拟化层；你必须使用相同类型的虚拟化" -"硬件因为 FreeBSD 设备名和驱动相关联。如果创建镜像环境中根块设备或者第一个网卡" -"和你生产环境不一样，那么在生产环境中使用镜像会产生错误。" - -msgid "" -"Canonical maintains an official set of Ubuntu-based images." -msgstr "" -"Canonical 维护 Ubuntu" -"系列官方镜像集。" - -msgid "CentOS 6 images" -msgstr "CentOS 6 镜像" - -msgid "CentOS 7 images" -msgstr "CentOS 7 镜像" - -msgid "CentOS directory: centos/6/os/x86_64" -msgstr "CentOS 目录： centos/6/os/x86_64" - -msgid "CentOS images" -msgstr "CentOS 镜像" - -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 "" -"选择 \"OpenSSH server\" 以便在 OpenStack 中启动虚拟机时你能 SSH 登陆到虚拟" -"机。" - -msgid "Choose URL as the installation method." -msgstr "选择 URL 安装方法。" - -msgid "Choose the VNC or text mode to set the installation options." -msgstr "安装选项选择 VNC 或者 文本模式。" - -msgid "CirrOS (test) images" -msgstr "CirrOS (测试镜像) " - -msgid "" -"CirrOS is a minimal Linux distribution that was designed for use as a test " -"image on clouds such as OpenStack Compute. You can download a CirrOS image " -"in various formats from the CirrOS download page." -msgstr "" -"CirrOS 是一个最小化的 Linux 发行版，它被设计为用于诸如 OpenStack 云计算测试用" -"镜像。你可以从 CirrOS " -"下载页面下载不同格式的 CirrOS 镜像。" - -msgid "Clean up (remove MAC address details)" -msgstr "清理（删除 MAC 地址相关信息）" - -msgid "Clean up and remove MAC address details." -msgstr "清除和删除 MAC 地址。" - -msgid "Clean up when you're done:" -msgstr "当完成操作后，清理命令“" - -msgid "" -"Click one of the HTTP links in the right-hand column next " -"to one of the mirrors." -msgstr "单击镜像中靠近右变的一列的其中一个 HTTP 链接。" - -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 "" -"点击 左上方的 \"New\" 按钮并跟随接下来的向导。，你将看到一" -"系列允许你指定虚拟机的详细信息的的对话框。" - -msgid "Click the isos/ folder link." -msgstr "点击isos/ 文件夹的链接。" - -msgid "Click the x86_64/ folder link for 64-bit images." -msgstr "要下载64位的文件点击 x86_64/ 文件夹链接。" - -msgid "" -"Click the folder link of the CentOS version that you want to use. For " -"example, 6.4/." -msgstr "" -"单击要使用的CentOS版本的文件夹链接。例如， 6.4 / 。" - -msgid "" -"Click the netinstall ISO image that you want to download. For example, " -"CentOS-6.4-x86_64-netinstall.iso is a good choice " -"because it is a smaller image that downloads missing packages from the " -"Internet during installation." -msgstr "" -"点击你想下载的网络安装ISO镜像文件，例如： CentOS-6.4-x86_64-" -"netinstall.iso 就是一个好的选择，因为它文件尺寸更小，在安装的时" -"候，其余的包可以通过网络下载。" - -msgid "" -"Cloudbase Solutions hosts an OpenStack Windows Server 2012 Standard Evaluation image " -"that runs on Hyper-V, KVM, and XenServer/XCP." -msgstr "" -"Cloudbase Solutions 存放了可运行在 Hyper-V, KVM, 以及 XenServer/XCP 上的" -"OpenStack Windows " -"Server 2012 标准版评估镜像。" - -msgid "" -"Common image properties are also specified in the /etc/glance/" -"schema-image.json file. For a complete list of valid property " -"keys and values, refer to the OpenStack Command-Line Reference." -msgstr "" -"通用的镜像属性可以在 /etc/glance/schema-image.json 文件" -"设定。要获取有效的属性值和数值，参考 OpenStack Command-Line Reference." - -msgid "" -"Complete the VirtIO drivers installation by running the following command:" -msgstr "使用以下命令完成VirtIO驱动的安装：" - -msgid "" -"Compute's ImagePropertiesFilter value is specified " -"in the value in the /etc/nova/nova.conf file." -msgstr "" -"计算节点的 ImagePropertiesFilter 值在 /" -"etc/nova/nova.conf 文件的 参数设定。" - -msgid "Configuration option=Default value" -msgstr "配置属性=默认值" - -msgid "Configure TCP/IP" -msgstr "配置 TCP/IP" - -msgid "Configure console" -msgstr "配置 console" - -msgid "" -"Configure the primary network interface to use DHCP. In this example, which " -"uses a virtio network device, this interface is named vtnet0." -msgstr "" -"配置首选网卡使用DHCP，在这个示例中，使用 virtio 网卡，在虚拟机中命名为 " -"vtnet0。" - -msgid "Configure to fetch metadata" -msgstr "配置获取metadata" - -msgid "" -"Consider using other mirrors as an alternative to mirror.umd.edu." -msgstr "" -"考虑使用其他镜像作为 mirror.umd.edu 的替代，国内推荐使用" -"mirrors.163.com ." - -msgid "Container formats" -msgstr "容器格式" - -msgid "Converting between image formats" -msgstr "转换镜像格式" - -msgid "" -"Converting images from one format to another is generally straightforward." -msgstr "转换一种镜像格式到另一种通常是直接的。" - -msgid "Create a 15GB qcow2 image:" -msgstr "创建一个15GB大小的磁盘镜像：" - -msgid "" -"Create a new LVM partition with the additional space. For example, " -"." -msgstr "在额外的空间上创建 LVM 分区。例如： 。" - -msgid "Create a new physical volume. For example, ." -msgstr "创建新的物理卷(PV)。例如： 。" - -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 "" -"使用以下内容创建模板文件（我们叫做 centos64.tdl）。你仅" -"仅需要修改 <rootpw> 部分的内容。" - -msgid "Create images manually" -msgstr "手动创建镜像" - -msgid "Create two partitions:" -msgstr "创建两个分区：" - -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 "" -"创建新的虚拟机镜像是安装完 OpenStack 意外的事情。你在你的系统上手工创建新虚拟" -"机镜像并且上传到云。" - -msgid "" -"Depending on the version of CentOS, the net installer requires the user to " -"specify either a URL or the web site and a CentOS directory that corresponds " -"to one of the CentOS mirrors. If the installer asks for a single URL, a " -"valid URL might be http://mirror.umd.edu/centos/6/os/x86_64." -msgstr "" -"不同版本的 CentOS ，网络安装程序可能要求用户指定 URL 或者网站地址和 对应的" -"CentOS其中一个镜像的CentOS目录，如果安装程序要求填入单个 URL ，一个有效的 " -"URL 可能是 http://mirror.umd.edu/centos/6/os/x86_64。" - -msgid "Detach the CD-ROM and reboot" -msgstr "卸载 CD-ROM 并重启" - -msgid "" -"Detect if any additional space is available on the disk. For example, parse " -"the output of ." -msgstr "检查磁盘额外可用空间。例如，解析 的输出。" - -msgid "Disable firewall" -msgstr "禁用防火墙" - -msgid "" -"Disable the default zeroconf route for the instance to " -"access the metadata service:" -msgstr "禁用默认的 zeroconf 路由。" - -msgid "Disable the zeroconf route" -msgstr "禁用 zeroconf 路由" - -msgid "Disk and container formats for images" -msgstr "镜像的磁盘格式和镜像的容器格式" - -msgid "Disk formats" -msgstr "磁盘格式" - -msgid "" -"Disk partitioning is a critical element of the image creation process and " -"the auto-generated default partitioning scheme does not work with " -"bsd-cloudinit at this time." -msgstr "" -"磁盘分区在镜像创建过程中是一个重要的要素，它自动产生默认的分区表会导致 " -"bsd-cloudinit 不起作用。" - -msgid "" -"Disk partitions and resize root partition on boot (cloud-init)" -msgstr "磁盘分区以及在启动时调整根分区大小 (cloud-init)" - -msgid "Disk partitions and resize root partition on boot (cloud-init)" -msgstr "磁盘分区以及在启动时调整根分区大小 (cloud-init)" - -msgid "Diskimage-builder" -msgstr "镜像生成器" - -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 "" -"不要使用这些工具修改正在运行的虚拟机镜像，这些工具被设计成只能修改未运行的虚" -"拟机镜像。" - -msgid "" -"Download a Fedora ISO " -"image. This procedure lets you create a Fedora 20 image." -msgstr "" -"下载一个 Fedora ISO 镜" -"像。这个过程将会创建Fedora 20 镜像。" - -msgid "Download a CentOS install ISO" -msgstr "下载 CentOS 安装 ISO" - -msgid "" -"Download a Windows Server 2012 installation ISO. Evaluation images are " -"available on the Microsoft website (registration " -"required)." -msgstr "" -"下载 Windows Server 2012 安装ISO文件，评估镜像文件可以在 微" -"软网站 (需注册)。" - -msgid "Download an Ubuntu install ISO" -msgstr "下载一个 Ubuntu 安装 ISO" - -msgid "Download and install Cloudbase-Init:" -msgstr "下载并安装 Cloudbase-Init：" - -msgid "" -"Download the latest bsd-cloudinit-installer. The " -"download commands differ between FreeBSD 10.1 and 9.2 because of differences " -"in how the command handles HTTPS URLs." -msgstr "" -"下载最新的 bsd-cloudinit-installer，在 FreeBSD " -"10.1 以及 9.2上的下载命令不一样，因为如何处理 HTTPS URL的方式" -"不一样。" - -msgid "" -"Download the signed VirtIO drivers ISO from the Fedora " -"website." -msgstr "" -"从Fedora 网站.下载已数字签名的 " -"VirtIO 驱动ISO文件。" - -msgid "Enable the VirtIO drivers." -msgstr "启用 VirtIO 驱动" - -msgid "Ensure image writes boot log to console" -msgstr "确认镜像输出启动日志到控制台" - -msgid "Ensure ssh server runs" -msgstr "确保 ssh 服务在运行" - -msgid "Example guestfish session" -msgstr "guestfish 修改示例：" - -msgid "Example: CentOS image" -msgstr "示例：CentOS 镜像" - -msgid "Example: Fedora image" -msgstr "示例：Fedora 镜像" - -msgid "Example: FreeBSD image" -msgstr "示例：FreeBSD 镜像" - -msgid "Example: Microsoft Windows image" -msgstr "示例：微软Windows镜像" - -msgid "Example: Ubuntu image" -msgstr "示例：Ubuntu 镜像" - -msgid "" -"Extend the logical volume contained the root partition by the amount of " -"space. For example, ." -msgstr "使用分区所有空间扩展包含根分区的逻辑卷（LV）。例如，。" - -msgid "" -"Extend the volume group with this physical partition. For example, " -"." -msgstr "使用这个屋里分区扩展卷组（VG）。例如： 。" - -msgid "Final config" -msgstr "Final config" - -msgid "First partition: A 64kB freebsd-boot partition with no mount point." -msgstr "第一个分区：一个64kB freebsd 启动分区，无挂载点。" - -msgid "Follow these steps to prepare the installation:" -msgstr "按照这些步骤做安装前准备：" - -msgid "" -"For a Linux-based image to have full functionality in an OpenStack Compute " -"cloud, there are a few requirements. For some of these, you can fulfill the " -"requirements by installing the cloud-init package. " -"Read this section before you create your own image to be sure that the image " -"supports the OpenStack features that you plan to use." -msgstr "" -"要使基于 Linux的镜像在 OpenStack 云计算中有全部的功能，有几个必要条件。其中你" -"可以安装 cloud-init软件包来完成。在你创建镜像之前，阅读这" -"一章节，以便明确你想要使用的镜像支持 OpenStack 的哪些特性。" - -msgid "" -"For example, to mount the root partition from our centos63_desktop." -"qcow2 image to /mnt, we can do:" -msgstr "" -"例如，挂载 centos63_desktop.qcow2镜像内的根分区到 " -"/mnt目录，可以敲以下命令：" - -msgid "" -"For information about libvirt images in OpenStack, see The life of an " -"OpenStack libvirt image from Pádraig Brady." -msgstr "" -"关于 Openstack 中的 libvirt 镜像信息，参考 The life of an OpenStack " -"libvirt image from Pádraig Brady." - -msgid "" -"For more information on configuring Grub, see ." -msgstr "关于配置Grub的详细信息，请参考 ." - -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 "" -"对于某些类型的修改，你可以使用更简单的方式直接挂载镜像内文件系统。" -" 程序，同样出自于 libguestfs 项目。" - -msgid "" -"For the command to work properly on CentOS 6." -"x, you might need to add the following lines to " -"the /boot/grub/menu.lst file:" -msgstr "" -"要使 命令在 CentOS 6.x 生效 ,你" -"需要添加以下文字到 /boot/grub/menu.lst 文件：" - -msgid "" -"For the command to work properly on Fedora 20, you might " -"need to add the following lines to the /boot/grub/menu.lst file:" -msgstr "" -"要让 命令在 Fedora 20虚拟机上，你需要编辑 /boot/" -"grub/menu.lst 文件添加以下几行。" - -msgid "" -"For the instance to access the metadata service, you must disable the " -"default zeroconf route:" -msgstr "要让虚拟机访问元数据服务，必须禁用 zeroconf 路由：" - -msgid "" -"FreeBSD 9.2 does not support peer-verification for https. " -"For FreeBSD 9.2, run this command:" -msgstr "" -"FreeBSD 9.2 不支持https对端认证,FreeBSD 9.2运行以下命令" - -msgid "From inside the instance, as root:" -msgstr "在虚拟机内，以root用户运行：" - -msgid "" -"From the list of services to start on boot, you must select ssh. Optionally, select other services." -msgstr "" -"从启动时需要启动的服务列表中选择 ssh 。以及可选的其他服务。" - -msgid "" -"Further customization could be accomplished by setting environment variables " -"or adding elements to the command-line:" -msgstr "更进一步的镜像定制可以通过设置环境变量或者添加元素到命令行：" - -msgid "Get images" -msgstr "获取镜像" - -msgid "Get the installer ISO:" -msgstr "获取安装ISO文件：" - -msgid "Go further with guestfish" -msgstr "guestfish更多功能" - -msgid "" -"Here is an example of how to use to resize an image. Assume " -"we have a 16GB Windows image in qcow2 format that we want to resize to 50GB. " -"First, we use to identify the partitions:" -msgstr "" -"这是一个使用 改变镜像大小的简单示例。假设我们有一个16GB的 " -"qcow2 格式的 Windows 镜像想要改变大小到50GB。首先，识别分区：" - -msgid "Hostname" -msgstr "主机名" - -msgid "ISO" -msgstr "ISO" - -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 "" -"如果 console=ttyS0 不存在，你需要修改 grub 配置，通常，你" -"不应该直接更新 grub.cfg 文件，因为它是程序自动生成的。" -"作为替代的，你应该编辑 /etc/default/grub 文件并修改 " -"GRUB_CMDLINE_LINUX_DEFAULT 的值： " - -msgid "" -"If both the XenAPI agent and cloud-init are present in an " -"image, cloud-init handles ssh-key injection. The system " -"assumes cloud-init is present when the image has the " -"cloud_init_installed property." -msgstr "" -"如果镜像内同时包含 XenAPI 和 cloud-init 包，" -"cloud-init包处理ssh-key的注入。当镜像有 " -"cloud_init_installed 属性的时候系统假设镜像已经安装" -"cloud-init 包。" - -msgid "" -"If building the image for Wheezy, packages like cloud-init, cloud-utils or cloud-initramfs-" -"growroot will be pulled from wheezy-backports. Also, the current " -"version of bootlogd in Wheezy doesn't support logging to " -"multiple consoles, which is needed so that both the OpenStack Dashboard " -"console and the console works. However, a fixed version is available from the " -"non-official GPLHost repository. To install it on top of the image, " -"it is possible to use the option of the " -"script, with this kind of script as parameter: " -msgstr "" -"如果你创建 Wheezy 镜像，诸如 cloud-init, cloud-" -"utils 或 cloud-initramfs-growroot 安装包将从 " -"wheezy-backports 获取。并且，当前版本的 Wheezy 的 bootlogd包不支持记录日志到多个控制台，但OpenStack Dashboard 控制台和 " -" 需要记录日志到多控制台才能工作。因此， GPLHost 软件库的修正的非官方版本。要在镜像上安装它，可能需要使用 脚本的 " -" 选项，使用下面的脚本作为参数：" - -msgid "" -"If prompted about which type of devices your installation uses, choose " -"Basic Storage Devices." -msgstr "" -"如果提示你使用哪种类型存储设备，选择 Basic Storage Devices。 " - -msgid "" -"If the account you use to ssh into your server does not have permissions to " -"run libvirt, but has sudo privileges, do:" -msgstr "" -"如果你的账户没有权限和libirt交互，但是有 sudo 权限，运行：" - -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 "" -"如果镜像有多个分区，使用显示分区为单独的设备（如：/" -"dev/mapper/loop0p1），然后挂载对应根文件系统的分区：" -"" - -msgid "" -"If the image has, say three partitions (/boot, /, swap), there should be one " -"new device created for each partition:" -msgstr "" -"如果镜像有三个分区（/boot, /, swap），对应的每个分区应该有新设备文件建立：" - -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 "" -"如果镜像显示有三个分区，对应的每个分区会有新的设备文件创建： " -"要挂载第二个分区，用 root 执行： 当所有操作完成后，清理操作：" -"" - -msgid "" -"If the image only has a single partition, you can mount the loop device " -"directly:" -msgstr "如果镜像只有一个分区，你可以直接挂载环回设备：" - -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 "" -"如果镜像分区使用LVM管理，在你使用 和 命令" -"后，你需要使用 和 来列出LVM分区设备以便这" -"些分区能被挂载：" - -msgid "" -"If the image partitions are not managed with LVM, they can be mounted " -"directly:" -msgstr "如果镜像分区没有使用LVM，那么可以直接挂载他们：" - -msgid "" -"If the installer asks for web site name and CentOS directory separately, you " -"might enter:" -msgstr "如果安装程序要求分别指定网站地址和 CentOS 目录，你可以这样输入：" - -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 "" -"如果你选择的网络块设备已经被占用，最开始的 命令将会失败，并" -"且 /dev/nbd3p{1,2,3} 设备文件也不会被建立。" - -msgid "If the network is not active, start it by doing:" -msgstr "如果网络未激活，输入以下命令：" - -msgid "" -"If unsure, use the default partition scheme for the installer because no " -"scheme is better than another." -msgstr "" -"如果你不太确定，使用默认的分区方案就可以了，因为没有一定说某个方案就比其他方" -"案要优秀。" - -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 "" -"如果你不太确定如何分区，我们推荐你使用安装程序默认的分区方案，因为目前也没有" -"任何方案完全优于其他分区方案。" - -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 "" -"如果我们预先不知道镜像内的分区挂载点，可以使用-i（检阅）参" -"数告诉 guestmount 自动检测挂载点：当挂载完成后，我们可以干一" -"些诸如使用rpm命令查看软件包安装列表等类似的事： 当一切都完成" -"后，卸载它：" - -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 "" -"如果你在无图形的服务器上创建虚拟机镜像，但在你本地机器有 X server启动，你可以" -"用 ，通过使用ssh X11 转发访问图形界面。因为 virt-manager " -"和 libvirt 直接交互，你通常需要 root 权限来访问。如果你能直接以 root 用户（或" -"者有权限和livbirt交互的用户） ssh 访问服务器，使用以下命令：" - -msgid "" -"If you are not able to install the cloud-init package in your image, to fetch the ssh public key and add it to " -"the root account, edit the /etc/rc.d/rc.local file and " -"add the following lines before the line touch /var/lock/subsys/" -"local:" -msgstr "" -"如果你不能在镜像中安装cloud-init软" -"件包，就获取ssh公钥并添加到root帐号中，编辑/etc/rc.d/rc.local文件，在touch /var/lock/subsys/local之前添加以下" -"内容：" - -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 "" -"如果你没有或者不希望安装 cloud-init包到虚拟机里，你可以自" -"己编写脚本来获取公钥并存放到用户账户内。" - -msgid "" -"If you are using , the commands should look something like " -"this:" -msgstr "如果你使用 命令，示例命令如下：" - -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 "" -"如果你能安装 cloud-utils 和 cloud-init包，我们推荐你创建" -"镜像时，只创建一个 ext3 和 ext4 分区（且不使用LVM管理）" - -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 "" -"如果你不能安装 cloud-initramfs-tools 软件包，Robert " -"Plestenjak 在 GitHub 上有个项目叫 linux-rootfs-resize ，包含了脚本更新" -"ramdisk，在ramdisk内使用 命令因此在启动的时候镜像尺寸缩放已" -"经就绪。" - -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 "" -"如果你不能安装 cloud-init 和 cloud-tools 软件包到镜像内但你还想镜像支持伸缩大小，你必须编写脚本让你的镜像在启" -"动的时候修改分区表。在这种情况下，我们推荐使用 LVM 来管理你的磁盘分区。由于 " -"Linux 内核限制（本文档编写时），当磁盘有分区被挂载的时候你不能修改磁盘分区" -"表，但是你可以使用 LVM 。" - -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 "" -"如果你删除网络持久规则文件，系统启动时你会看到内核警告信息，这是为什么我们推" -"荐使用空文件替代的原因。" - -msgid "" -"If you do not use LVM, you must modify the table to extend the existing root " -"partition to encompass this additional space." -msgstr "" -"如果你没使用 LVM,你需要修改分区表扩充已经存在的根分区包纳磁盘额外的空间。" - -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 "" -"如果你不想使用 virt-manager （例如，你不想安装依赖包到你的服务器，你本地机器" -"没有 X server 或者 X11 转发工作不正常），你可以使用 工具通" -"过 Libvirt 启动虚拟机，然后使用本地 VNC 客户端连接到虚拟机的图形控制台。" - -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 "" -"如果你不能使用libguestfs，你可以使用loop(环回)设备，kpartx,网络块设备直接挂载" -"镜像文件系统到宿主机系统。" - -msgid "" -"If you have a raw virtual machine image that is not using LVM to manage its " -"partitions, use the command to find an unused loop device. " -"" -msgstr "" -"如果你有未使用LVM管理分区的裸虚拟机镜像。首先，使用命令查找系" -"统未使用的环回设备。" - -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:" -msgstr "" -"如果你忘记使用 -u 参数，或者你想编辑文件做额外的定制化，" -"你可以使用 命令，来使用 创建的libvirt XML " -"文件，例如：" - -msgid "" -"If you modify this example, the root partition, which is mounted on " -"/, must be the last partition on the drive so that it " -"can expand at run time to the disk size that your instance type provides. " -"Also note that bsd-cloudinit currently has a hard-" -"coded assumption that this is the second partition." -msgstr "" -"如果你的分区和示例不一样，挂载到 / 的根分区必须是磁盘上" -"的最后一个分区，以便在启动新虚拟机实例时能够扩展分区大小。同时注意 " -"bsd-cloudinit 目前将假设根分区是磁盘的第二个分区且" -"已硬编码到程序中。" - -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 " -"that will let you view and interact with the guest's graphical console." -msgstr "" -"如果你计划创建虚拟机镜像的机器能运行 X11 程序，最简单的方法是使用 " -" 图形界面，可以在 Fedora 系列和 Debian 系列系统上安装 " -"virt-manager 软件包。它的图形界面内含 VNC 客户端使你能和虚" -"拟机图形界面进行交互。" - -msgid "" -"If you use , the commands should look something like this:" -msgstr "如果你使用 ，命令应该如下所示：" - -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 "" -"如果你使用了LVM，你可以添加新 LVM 条目到分区表，创建新 LVM 物理卷，然后添加 " -"LVM 物理卷到 卷组，然后扩充 root 卷的容量。" - -msgid "" -"If you use the OpenStack XenAPI driver, the Compute service automatically " -"adjusts the partition and file system for your instance on boot. Automatic " -"resize occurs if the following conditions are all true:" -msgstr "" -"如果你使用 OpenStack XenAPI 驱动，那么计算服务在虚拟机启动时会自动调整分区和" -"文件系统大小。在满足以下条件的时候会自动调整容量需：" - -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 "" -"如果你想修改镜像让他在启动时加载8021q内核模块，你必须在/etc/" -"sysconfig/modules/目录下简历一个可执行脚本。你可以使用" -"guestfish命令创建一个空文件，然后使用 命令编" -"辑它，然后使用 命令让它具有可执行权限。 我们" -"添加以下一行到文件内，然后保存：然后设置文件可执行权限：" -"" - -msgid "" -"If you wish to build your own images of Debian 7.0 (aka Wheezy, the current " -"stable release of Debian), you can use the package which is used to build " -"the official Debian images. It is named openstack-debian-images, and it provides a simple script for building them. This package is " -"available in Debian Unstable, Debian Jessie, and through the wheezy-" -"backports repositories. To produce a Wheezy image, simply run: " -"" -msgstr "" -"如果你想创建 Debian 7.0 镜像（也就是 Wheezy，Debian 当前稳定版本）。你可以使" -"用用于创建官方的 Debian 镜像的 openstack-debian-images 软" -"件包，它提供既简单的脚本来创建。这个包在 Debian 未稳定分支 Debian Jessie 内，" -"通过使用 wheezy-backports 源。要生成 Wheezy 镜像，仅需运行：" - -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, and Linux, VirtualBox stores images by default in " -"the ~/VirtualBox VMs/ directory. The following example " -"creates a raw image in the current directory from a VirtualBox VDI image." -msgstr "" -"如果你使用 VirtualBox 创建了一个 VDI 镜像，你可以使用VirtualBox附带的 " -" 工具转换它为raw格式，在 Mac OS X和Linux 上,VirtualBox 默认存" -"放镜像在 ~/VirtualBox VMs/ 目录，以下示例在当前目录中从" -"一个VirtualBox VDI镜像创建一个 raw 镜像。" - -msgid "" -"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " -"format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.4-x86_64-disk.img. " -msgstr "" -"如果你部署的使用 QEMU 或者 KVM，我们推荐使用 QCOW2 镜像格式，本文档编写时最近" -"的64位 qcow2 镜像是 cirros-0.3.4-x86_64-disk.img。" - -msgid "" -"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " -"format. The most recent version of the 64-bit QCOW2 image for Ubuntu 14.04 " -"is trusty-server-cloudimg-amd64-disk1.img." -msgstr "" -"如果你的部署使用 QEMU 或者 KVM，推荐使用 qcow2 镜像格式。本文档编写时最新的 " -"64位 Ubuntu 14.04 qcow2 镜像是trusty-server-" -"cloudimg-amd64-disk1.img。" - -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 "" -"如果你的镜像使用 grub2 做为引导程序，在配置文件内应该有一行配置内容。例如， " -"/boot/grub/grub.cfg，看起来应该如下：" - -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 "如果你镜像分区使用了LVM，使用前面介绍的 losetup 和 kpartx 显示分区：" - -msgid "Image cache management configuration options" -msgstr "镜像缓存管理配置选项" - -msgid "Image format" -msgstr "镜像格式" - -msgid "Image is complete" -msgstr "镜像准备完成" - -msgid "Image metadata" -msgstr "镜像元数据" - -msgid "" -"Image metadata can help end users determine the nature of an image, and is " -"used by associated OpenStack components and drivers which interface with the " -"Image service." -msgstr "" -"镜像元数据使最终用户能获取镜像的原生特性，并且用于关联 OpenStack 的各组件以及" -"驱动镜像服务接口。" - -msgid "" -"Images are arranged by Ubuntu release, and by image release date, with " -"\"current\" being the most recent. For example, the page that contains the " -"most recently built image for Ubuntu 14.04 \"Trusty Tahr\" is http://cloud-images." -"ubuntu.com/trusty/current/. Scroll to the bottom of the page for " -"links to images that can be downloaded directly." -msgstr "" -"镜像被分类为 Ubuntu 发行版本，以及镜像发行日期，镜像发布的 \"current\" 是最" -"近的发行版。例如，页面包含的最近的 \"Trusty Tahr\" Ubuntu 14.04版本地址是 " -"http://" -"cloud-images.ubuntu.com/trusty/current/ 。拉动页面到最底下即可直接下" -"载。" - -msgid "" -"In FreeBSD 10.1 the command verifies SSL peers by default, " -"so you need to install the ca_root_nss package that " -"contains certificate authority root certificates and tell " -"where to find them. For FreeBSD 10.1 run these commands:" -msgstr "" -"在 FreeBSD 10.1 命令默认校验SSL对端，因此你需要安装 " -"ca_root_nss 包，它包含了根证书的认证授权信息以及告诉 " -" 如何找到根证书。 对于 FreeBSD 10.1运行下面的命令：" - -msgid "" -"In a CentOS cloud image, the login account is centos." -msgstr "CentOS 云镜像中的登陆账号是 centos." - -msgid "" -"In a CirrOS image, the login account is cirros. The " -"password is cubswin:)" -msgstr "" -"CirrOS 镜像的登陆账号是 cirros，密码是 " -"cubswin:)" - -msgid "In a Debian image, the login account is admin." -msgstr "在 Debian 镜像中，登陆账号是 admin。" - -msgid "" -"In a Fedora cloud image, the login account is fedora." -msgstr "在Fedora 云镜像中，登陆账户是 fedora." - -msgid "" -"In a RHEL cloud image, the login account is cloud-user." -msgstr "在红帽企业Linux云镜像中，登陆账户是 cloud-user。" - -msgid "" -"In addition to the ssh public key, an image might need additional " -"information from OpenStack, such as Provide user data " -"to instances, that the user submitted when requesting the image. For " -"example, you might want to set the host name of the instance when it is " -"booted. Or, you might wish to configure your image so that it executes user " -"data content as a script on boot." -msgstr "" -"除了 ssh 公钥，镜像可能还需要从 Openstack 中获取其他信息，例如当启动虚拟机获" -"取镜像的时候 提供虚机用户数据 ，以及你可" -"能在虚拟机启动的时候设置主机名，或者你可能希望配置镜像设置它在启动的时候执行" -"用户数据脚本。" - -msgid "" -"In an Ubuntu cloud image, the login account is ubuntu." -msgstr "Ubuntu 云镜像的登陆账号是 ubuntu。" - -msgid "" -"In general, we recommend that you disable any firewalls inside of your image " -"and use OpenStack security groups to restrict access to instances. The " -"reason is that having a firewall installed on your instance can make it more " -"difficult to troubleshoot networking issues if you cannot connect to your " -"instance." -msgstr "" -"通常，我们推荐你关闭掉镜像内所有的防火墙，使用 OpenStack 安全组来限制访问你的" -"虚拟机。因为在镜像内开启防火墙会增加在不能访问虚拟机的时候诊断问题时的难度。" - -msgid "" -"In the /var/log/compute/compute.log file, look for the " -"identifier:" -msgstr "" -"在 /var/log/compute/compute.log 文件，查看以下部分日" -"志。" - -msgid "" -"In the configuration options window, change the " -"following settings:" -msgstr "在configuration options窗口，修改以下设置：" - -msgid "" -"In the example above, the guest centos-6.4 uses VNC " -"display :1, which corresponds to TCP port 5901. You should be able to connect a VNC client running on your local " -"machine to display :1 on the remote machine and step through the " -"installation process." -msgstr "" -"在上面的示例中，虚拟机 centos-6.4 使用 VNC 显示器 " -":1，对应的 TCP 端口是 5901。你应该使用" -"本地 VNC 客户端连接到远程服务器的 ：1 显示器并且完成安装步骤。" - -msgid "" -"In the previous example, you paused the instance, ejected the disk, and " -"unpaused the instance. In theory, you could have ejected the disk at the " -"Installation complete screen. However, our testing " -"indicates that the Ubuntu installer locks the drive so that it cannot be " -"ejected at that point." -msgstr "" -"在前面的示例中，你暂停虚拟机，弹出磁盘，然后恢复虚拟机，理论上，你在 " -"Installation complete 屏幕显示的时候就能弹出磁盘，然后" -"我们测试显示 Ubuntu 安装程序锁定了磁盘，因此，不能弹出磁盘。" - -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 "" -"在这个示例中，/dev/sda2是我们需要修改大小的分区，我们创" -"建一个新的 qcow2 镜像并且使用 命令写入一个修改大小后的原始镜" -"像文件到新镜像文件内：" - -msgid "" -"In this example, /dev/loop0 is free. Associate a loop " -"device with the raw image:" -msgstr "" -"在这个示例中，/dev/loop0是空闲的，关联裸镜像到环回设备：" -"" - -msgid "" -"Install cloud-init package inside the Fedora guest by " -"adding the EPEL repo:" -msgstr "" -"在 Fedora 虚拟机添加 EPEL 源以便安装 cloud-init 软件包。" - -msgid "" -"Install sudo and configure the freebsd " -"user to have passwordless access:" -msgstr "" -"安装 sudo 并且配置 freebsd 用户无密码访" -"问：" - -msgid "Install GRUB boot loader" -msgstr "安装 GRUB 引导程序" - -msgid "" -"Install a cloud-init RPM, which " -"is a port of the Ubuntu cloud-init package. This is the recommended approach." -msgstr "" -"安装从 Ubuntu cloud-" -"init 移植过来的cloud-init " -"RPM包，这也是推荐的方法。" - -msgid "" -"Install and run the acpid service on the guest system to " -"enable the virtual machine to reboot or shutdown an instance." -msgstr "" -"在虚拟机上安装并且启用 acpid 服务，以便能够重启或者关闭虚" -"拟机。" - -msgid "Install cloud-init" -msgstr "安装 cloud-init" - -msgid "Install the cloud-init package:" -msgstr "安装 cloud-init 软件包：" - -msgid "Install the ACPI service" -msgstr "安装 ACPI 服务" - -msgid "Introduction" -msgstr "介绍" - -msgid "" -"Issue this command to download and install the latest bsd-" -"cloudinit package, and install the necessary prerequisites." -msgstr "" -"输入这个命令下载和安装最新的 bsd-cloudinit 包，并且安装包" -"的依赖包。" - -msgid "" -"KVM with virtio drivers is used as the virtualization platform because that " -"is the most widely used among OpenStack operators. If you use a different " -"platform for your cloud virtualization, use that same platform in the image " -"creation step." -msgstr "" -"这个示例中使用 KVM 以及 virtio 驱动做为虚拟化平台，因为这是 Openstack 使用最" -"广泛的平台之一，如果你使用其他平台做为你的云计算虚拟化，在创建中镜像也使用相" -"同的平台。" - -msgid "" -"Launch a VM on your local workstation. Use the same hypervisor, virtual " -"disk, and virtual network drivers as you use in your production environment." -msgstr "启动一个虚拟机，使用和你生产环境一样的虚拟化层，虚拟磁盘以及网卡驱动。" - -msgid "Log in as administrator and start a command window." -msgstr "以administrator用户登录并开启命令行窗口。" - -msgid "" -"Log in as root user when you boot for the first time after installation." -msgstr "安装完成重启后以root用户登录。" - -msgid "Log in to newly created image" -msgstr "登陆到新创建的镜像内" - -msgid "Loop devices, kpartx, network block devices" -msgstr "loop(环回)设备，kpartx,网络块设备" - -msgid "Make a virtual drive:" -msgstr "创建一个虚拟磁盘：" - -msgid "Manage the image cache" -msgstr "管理镜像缓存" - -msgid "" -"Metadata can also determine the scheduling of hosts. If the " -"option is set on an image, and Compute is configured so that the " -"ImagePropertiesFilter scheduler filter is enabled " -"(default), then the scheduler only considers compute hosts that satisfy that " -"property." -msgstr "" -"元数据还能探测知主机的调度。 如果设置了镜像的 选项，而且计算" -"节点也配置了启用（默认的） ImagePropertiesFilter 调" -"度过滤器。那么调度器在调度时只需要考虑哪些符合属性需求的计算节点。" - -msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." -msgstr "微软 Hyper-V 使用 VHD 镜像格式。" - -msgid "Microsoft Windows images" -msgstr "微软 Windows 镜像" - -msgid "Minimize boot delay:" -msgstr "最小启动延时：" - -msgid "" -"Modify /etc/rc.local to fetch desired information from " -"the metadata service, as described in the next section." -msgstr "" -"修改 /etc/rc.local 文件从元数据服务获取信息，具体将在下" -"一届描述。" - -msgid "Modify a single file inside of an image" -msgstr "修改镜像内单个文件" - -msgid "Modify images" -msgstr "更改镜像内容" - -msgid "Modify the partition table to make it aware of the additional space:" -msgstr "修改分区表识别磁盘额外的空间。" - -msgid "Mount a qcow2 image (with LVM)" -msgstr "挂载 qcow2 镜像（有LVM）" - -msgid "Mount a qcow2 image (without LVM)" -msgstr "挂载 qcow2 镜像（无LVM）" - -msgid "Mount a raw image (with LVM)" -msgstr "挂载裸镜像（有LVM）" - -msgid "Mount a raw image (without LVM)" -msgstr "挂载裸镜像（无LVM）" - -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 "" -"使用本节介绍的工具挂载一个不受信任的虚机镜像有安全风险，如果你需要访问虚拟机" -"镜像内的内容，请使用 libguestfs 项目的工具诸如 guestfish 和 guestmount 。查看" -"由Daniel Berrangé 写的A reminder why you should never mount guest disk images on " -"the host OS为什么不要挂载虚拟机磁盘镜像到宿主机系统的提示 获取更多细节" -"内容。" - -msgid "" -"Navigate to the CentOS mirrors page." -msgstr "" -"浏览 CentOS 镜像" -" 页面。" - -msgid "" -"Network adapter to configure: Red Hat VirtIO Ethernet Adapter" -msgstr "网卡：Red Hat VirtIO Ethernet Adapter" - -msgid "" -"Next, update the grub configuration. On Debian-based operating-systems such " -"as Ubuntu, run this command:" -msgstr "然后，更新 grub 配置，在 Debian 系列的系统如 Ubuntu，运行以下命令：" - -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 "" -"下一步，我们想删除一个文件，使用guestfish 命令 ，就像使用普" -"通shell命令一样。" - -msgid "" -"Next, you need to use the command to identify the LVM " -"volume groups and then to expose the volumes as devices:" -msgstr "" -"下一步，你需要用 命令识别 LVM 卷组然后使用 " -"激活卷：" - -msgid "No hard-coded MAC address information" -msgstr "无硬编码的 MAC 地址信息" - -msgid "" -"Non-Xen with cloud-init/cloud-tools: One ext3/ext4 partition (no LVM, no /" -"boot, no swap)" -msgstr "" -"非 Xen 平台安装 cloud-init/cloud-tools ：单 ext3/ext4 分区（无 LVM ,无 /" -"boot , 无 SWAP）" - -msgid "" -"Non-Xen without cloud-init/cloud-tools: LVM" -msgstr "" -"非 Xen 环境且无 cloud-init/cloud-tools" -"软件包：使用 LVM" - -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 "" -"现在你可以上传虚拟机镜像到镜像服务了，所以不再需要 libvirt 来管理虚拟机镜像，" -"使用 命令来完成。" - -msgid "" -"Now that you can upload the image to the Image service, you no longer need " -"to have this virtual machine image managed by libvirt. Use the " -" command to inform libvirt:" -msgstr "" -"现在你可以上传虚拟机镜像到镜像服务了，不再需要 libvirt 来管理虚拟机镜像，使" -"用 命令完成。" - -msgid "OVF" -msgstr "OVF" - -msgid "Official Debian images" -msgstr "官方 Debian 镜像" - -msgid "Official Fedora images" -msgstr "官方Fedora 镜像" - -msgid "Official Red Hat Enterprise Linux images" -msgstr "红帽企业lLinux官方镜像" - -msgid "Official Ubuntu images" -msgstr "Ubuntu 官方镜像" - -msgid "Official images from other Linux distributions" -msgstr "其他Linux发行版的官方镜像" - -msgid "Official openSUSE and SLES images" -msgstr "官方 openSUSE 和 SLES 镜像" - -msgid "" -"On Fedora-based systems, such as RHEL and CentOS, and on openSUSE, run this " -"command:" -msgstr "在 Fedora 系列的系统，如 RHEL 和 CentOS，以及 openSUSE，运行以下命令：" - -msgid "" -"Once the installation is completed, the VM restarts. Define a password for " -"the administrator when prompted." -msgstr "安装完成，虚拟机重启后，为虚拟机administrator用户设置密码。" - -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 "" -"有时你拿到一个虚拟机镜像，但你在将它上传到 OpenStack镜像服务之前，你想要修改" -"镜像里的内容。这里介绍几个可以修改镜像的工具。" - -msgid "OpenStack" -msgstr "OpenStack" - -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 "" -"OpenStack 计算节点目前并不支持 OVF 包，如果你想要在Openstack中使用，你需要从" -"OVF中释放磁盘镜像文件。" - -msgid "OpenStack Foundation" -msgstr "OpenStack基金会" - -msgid "OpenStack Linux image requirements" -msgstr "OpenStack Linux 镜像需求" - -msgid "OpenStack Virtual Machine Image Guide" -msgstr "OpenStack 虚拟机镜像制作指南" - -msgid "Optionally, add users." -msgstr "可选的，添加用户。" - -msgid "Oz" -msgstr "Oz" - -msgid "" -"Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh " -"into the instance and perform the customizations." -msgstr "" -"Oz 将调用 libvirt 通过 KVM 来启动镜像，然后Oz ssh 到虚拟机内完成定制化工作。" - -msgid "Packer" -msgstr "Packer" - -msgid "" -"Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux " -"kernel version < 3.0)" -msgstr "" -"Linux 内核对半虚拟化 Xen的支持 (Xen hypervisor only with Linux kernel " -"version < 3.0)" - -msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" -msgstr "内核内对半虚拟化的 Xen 支持（仅Xen 虚拟化）" - -msgid "Partition the disks" -msgstr "磁盘分区" - -msgid "Point the installer to a CentOS web server" -msgstr "将安装程序指向 CentOS 网站。" - -msgid "Power off the system:" -msgstr "关闭系统：" - -msgid "" -"Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel " -"did not have support for paravirtualized Xen virtual machine instances (what " -"Xen calls DomU guests). If you are running the Xen hypervisor with " -"paravirtualization, and you want to create an image for an older Linux " -"distribution that has a pre 3.0 kernel, you must ensure that the image boots " -"a kernel that has been compiled with Xen support." -msgstr "" -"在 Linux 内核 3.0以前，内核的主线分支不支持 Xen 半虚拟化虚拟机（即 Xen DomU " -"虚拟机）。如果你运行 Xen 半虚拟化，并且你想创建内核在3.0版本之前的虚拟机镜" -"像，你不许确保镜像启动内核已经编译了 Xen 支持。" - -msgid "Process user data and other metadata (cloud-init)" -msgstr "处理用户以及其他的元数据 (cloud-init)" - -msgid "Process user data and other metadata (cloud-init)" -msgstr "处理用户数据以及其他元数据（cloud-init）" - -msgid "" -"Provide a host name for your image. If you use bsd-cloudinit, it overrides this value with the name provided by OpenStack " -"when an instance boots from this image." -msgstr "" -"提供主机名。如果你使用 bsd-cloudinit，它将在虚拟机" -"启动时使用OpenStack分配给他的主机名覆盖这个值。" - -msgid "QCOW2 (KVM, Xen)" -msgstr "QCOW2 (KVM, Xen)" - -msgid "QED (KVM)" -msgstr "QED (KVM)" - -msgid "Rackspace Cloud Builders (multiple distros) images" -msgstr "Rackspace 云计算镜像（多个发行版）" - -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 "" -"Rackspace 云运行商维护了多个发行版（Red Hat, CentOS, Fedora, Ubuntu）预先创建" -"的镜像列表。列表的链接为rackerjoe/oz-image-build on GitHub。" - -msgid "Raw" -msgstr "Raw" - -msgid "Red Hat Enterprise Linux 6 KVM Guest Image" -msgstr "Red Hat Enterprise Linux 6 KVM Guest Image" - -msgid "Red Hat Enterprise Linux 7 KVM Guest Image" -msgstr "Red Hat Enterprise Linux 7 KVM Guest Image" - -msgid "" -"Red Hat maintains official Red Hat Enterprise Linux cloud images. A valid " -"Red Hat Enterprise Linux subscription is required to download these images." -msgstr "" -"红帽公司维护红帽企业lLinux官方镜像。下载这些镜像需要红帽企业Linux订阅。" - -msgid "Remaining licensing details are filled in by the template." -msgstr "其余的授权细节来自于模版" - -msgid "" -"Remove the HWADDR line from /etc/sysconfig/network-scripts/ifcfg-" -"eth0 on Fedora-based images." -msgstr "" -"在 Fedora系列的镜像上从 /etc/sysconfig/network-scripts/ifcfg-" -"eth0 文件删除 HWADDR 一行。" - -msgid "" -"Replace /etc/udev/rules.d/70-persistent-net.rules with " -"an empty file (contains network persistence rules, including MAC address)." -msgstr "" -"使用空文件替换 /etc/udev/rules.d/70-persistent-net.rules 文件（包含网络持久规则，包括MAC地址）。" - -msgid "" -"Replace /lib/udev/rules.d/75-persistent-net-generator.rules with an empty file (this generates the file above)." -msgstr "" -"使用空文件替换 /lib/udev/rules.d/75-persistent-net-generator." -"rules 文件（它将生成上面所说的文件）。" - -msgid "Resize an image" -msgstr "改变镜像大小" - -msgid "Resize the root file system. For example, ." -msgstr "重新改变根文件系统大小。例如，。" - -msgid "Resize the root volume file system." -msgstr "重改变 root 卷文件系统。" - -msgid "" -"Run the command to see a range of allowed --os-" -"variant options." -msgstr "" -"运行 命令查看 --os-variant 允许的选项范" -"围。" - -msgid "" -"Run the following command to convert a vmdk image file to a qcow2 image " -"file. " -msgstr "运行以下命令转换 VMDK 镜像文件到qcow2镜像文件，" - -msgid "" -"Run the following command to convert a vmdk image file to a raw image file. " -"" -msgstr "运行以下命令转换 VMDK 镜像文件到裸格式镜像文件，" - -msgid "" -"Run the following commands from the host to eject the disk and reboot using " -"virsh, as root." -msgstr "以root用户使用virsh命令弹出安装盘并且重启虚拟机。" - -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 "" -"以root用户使用virsh命令，执行下面的步骤完成挂载空磁盘并重启。如果你使用virt-" -"manager安装,下面的命令也起相同作用，你也可以使用图形界面卸载磁盘并手工停止然" -"后启动虚拟机。" - -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 "" -"在宿主机上以 root 用户运行以下命令暂停虚拟机，弹出磁盘然后恢复虚拟机。如果你" -"使用 virt-manager ，你需要在图形界面完成这个过程。" - -msgid "" -"Run the following commands inside the CentOS guest to install the ACPI " -"service and configure it to start when the system boots:" -msgstr "" -"在 CentOS虚拟机内运行以下命令安装 ACPI 服务并配置为系统启动时自动启动。" - -msgid "" -"Run the following commands inside the Fedora guest to install the ACPI " -"service and configure it to start when the system boots:" -msgstr "在 Fedora 虚拟机内运行一下命令安装并启用 ACPI服务。" - -msgid "Run the installer:" -msgstr "运行安装程序：" - -msgid "SSH server running" -msgstr "启用SSH服务" - -msgid "SUSE Studio" -msgstr "SUSE Studio" - -msgid "" -"SUSE provides images for openSUSE. For SUSE Linux Enterprise " -"Server (SLES), custom images can be built with a web-based tool called SUSE Studio. SUSE Studio can " -"also be used to build custom openSUSE images." -msgstr "" -"SUSE 为 openSUSE 提供镜像。对于SUSE 企业服务器版 Linux（SLES），定" -"制镜像可以通过基于web的一个工具 SUSE Studio来完成。SUSE Studio同时也可以用于定制openSUSE 镜像。" - -msgid "" -"Second partition: A freebsd-ufs partition with a mount " -"point of / with all remaining free space." -msgstr "" -"第二个分区： freebsd-ufs 分区挂载点是 / 并使用所有剩下的空余空间。" - -msgid "" -"See CentOS " -"mirror page to get a full list of mirrors, click on the \"HTTP\" link " -"of a mirror to retrieve the web site name of a mirror." -msgstr "" -"访问 CentOS " -"mirror page 获取全部镜像列表，点击 镜像的\"HTTP\"链接获取镜像网站名。" - -msgid "" -"Select \"Yes\" when asked about installing the GRUB boot loader to the " -"master boot record." -msgstr "当提示安装 GRUB 引导程序到硬盘主启动记录时，选择 \"Yes\"。" - -msgid "" -"Select Create to create a partition table. This " -"action is the default when no partition table exists. Then, select " -"GPT GUID Partition Table from the list. This choice is " -"the default." -msgstr "" -"选择 Create创建分区表，当没有分区表存在时这是默认动" -"作，然后，从列表中选择 GPT GUID Partition Table ，这也是" -"默认选择。" - -msgid "" -"Select Finish and then Commit " -"to commit your changes." -msgstr "" -"选择 Finish 然后选择 Commit 提" -"交修改。" - -msgid "Select a mirror" -msgstr "选择镜像站点" - -msgid "Select a root password." -msgstr "设置root用户密码。" - -msgid "Select the CMOS time zone." -msgstr "选择 CMOS 时区。" - -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 "" -"剩下的步骤中，选择默认的值即可。当安装完成时，你会看到提示移除 CD-ROM。" - -msgid "Select the time zone appropriate to your environment." -msgstr "选择你当前环境的时区。" - -msgid "Serial port for logging: COM1" -msgstr "日志输出串口：COM1" - -msgid "Set the disk format for your image to one of the following values:" -msgstr "设置你的镜像磁盘格式为下面的值：" - -msgid "" -"Set the timezone, network configuration, installation source, and the root " -"password. Optionally, you can choose to create a user." -msgstr "" -"设置时区，网络配置，安装源，root用户密码，以及作为可选项，你还可以创建额外的" -"用户。" - -msgid "Set up disk partitioning." -msgstr "设置磁盘分区。" - -msgid "Set up the console:" -msgstr "设置console:" - -msgid "Set up the installation destination as shown below:" -msgstr "设置安装位置：" - -msgid "Shut down the instance" -msgstr "关闭虚拟机" - -msgid "Shut down the instance from inside the instance as a root user:" -msgstr "在虚拟机内以root用户关闭虚拟机。" - -msgid "" -"Since January 2015, Debian provides images for direct download. They are now " -"made at the same time as the CD and DVD images of Debian. However, until " -"Debian 8.0 (aka Jessie) is out, these images are the weekly built images of " -"the testing distribution." -msgstr "" -"自 2015年1月开始，Debian 提供直接下载镜像。他们和 CD 以及 DVD 镜像同步，然" -"而，直到 Debian 8.0 (也称 Jessie)出来，这些镜像还是每周生成的测试发行版（译" -"者注：但貌似现在已经有8.1的正式版放出了）。" - -msgid "Software selection: OpenSSH server" -msgstr "软件选择：OpenSSH 服务" - -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 "" -"有些 VNC 客户会使用分号 (;)替换冒号(:) " -"以及用中划线 (-)替换下划线(_) ，确认你" -"输入的是 http: 而不是 http; ， " -"authorized_keys 而不是 authorized-keys。" - -msgid "" -"Some VNC clients replace the colon (:) with a semicolon " -"(;) and the underscore (_) with a " -"hyphen (-). Make sure to specify http: " -"and not http;. Make sure to specify " -"authorized_keys and not authorized-keys." -msgstr "" -"有些 VNC 客户会使用分号 (;)替换冒号(:) " -"以及用中划线 (-)替换下划线(_) ，确认你" -"输入的是 http: 而不是 http; ， " -"authorized_keys 而不是 authorized-keys。" - -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 "" -"有时，你必须删除虚拟机镜像内任何包含虚拟机安装时分配给虚拟机网卡的MAC的文件，" -"因为用镜像文件创建新虚拟机时网卡MAC地址和创建镜像的虚拟机并不一样。这个示例通" -"过删除 /etc/udev/rules.d/70-persistent-net.rules文件以及" -"删除/etc/sysconfig/network-scripts/ifcfg-eth0文件中" -"HWADDR一行来演示了如何使用guestfish删除镜像中和原MAC地址相" -"关联的地方。" - -msgid "" -"Start the Windows Server 2012 installation with the command:" -msgstr "使用命令开始 Windows Server 2012 的安装：" - -msgid "Start the install process" -msgstr "开始安装" - -msgid "Start the installation process" -msgstr "启动安装程序" - -msgid "" -"Start the installation process by using either or " -" as described in the previous section. If you use " -", do not forget to connect your VNC client to the virtual " -"machine." -msgstr "" -"使用在之前示例中讲解的 或者 命令。如果你使" -"用 ，记得使用 VNC 客户端连接到虚拟机。" - -msgid "" -"Start the installation process using either or " -" as described in the previous section. If you use " -", do not forget to connect your VNC client to the virtual " -"machine." -msgstr "" -"通过使用前面的章节介绍的 或者 命令都可以启" -"动安装程序，如果你使用 记得连接你的VNC客户端到虚拟机。" - -msgid "Start the installation using as shown below:" -msgstr "使用 开始安装 ，如下：" - -msgid "Step through the install" -msgstr "安装步骤" - -msgid "" -"Step through the install, using the default options. When prompted for a " -"user name, the default (ubuntu) " -"is fine." -msgstr "" -"安装过程中，使用默认的选项即可，当提示输入用户名时，使用默认的 (ubuntu) 即可。" - -msgid "Step through the installation" -msgstr "安装步骤" - -msgid "" -"Step through the installation, using the default options. The simplest thing " -"to do is to choose the \"Basic Server\" install (may be called \"Server\" " -"install on older versions of CentOS), which installs an SSH server." -msgstr "" -"使用默认设置，完成安装程序设置步骤，最后最简单的事选择 \"Basic Server\" 软件" -"包组（以前版本的 CentOS 可能叫做 \"Server\" ），它将默认安装 SSH 服务。" - -msgid "Storage devices" -msgstr "存储设备" - -msgid "Support for snapshots." -msgstr "支持快照。" - -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 "" -"\"raw\" 镜像格式是最最简单的，并且是被 KVM 和 Xen 原生支持的格式，你可以想象" -"裸格式镜像和块设备文件是二进制位相当的，就好像从块设备拷贝过来的，比方说，使" -"用 命令将 /dev/sda 内容拷贝到一个文件。" - -msgid "" -"The AMI/AKI/ARI format was the initial image format supported " -"by Amazon EC2. The image consists of three files:" -msgstr "" -"AMI/AKI/ARI 格式是亚马逊 EC2 云最初支持的格式，它包含三类文" -"件：" - -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 "" -"qcow2 " -"（QEMU 写时复制版本2）格式通常是KVM使用，相比裸格式，它有额外的特性，例如：" -"" - -msgid "" -"The libguestfs project " -"has a number of other useful tools, including:" -msgstr "" -" libguestfs项目还有其他一" -"堆有用的工具，包括" - -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 "" -" ISO 格式是磁盘镜像被格式化成只读 ISO 9660（ECMA-119） " -"文件系统的格式，通常用于 CD 和 DVD。通常 ISO 不被考虑是虚拟机镜像格式，由于他" -"包含一个可启动的文件系统，你可以将它看做是和其他虚拟机镜像文件一样。" - -msgid "" -"The Ubuntu Server Guide has " -"documentation on how to use VMBuilder to create an Ubuntu image." -msgstr "" -"Ubuntu Server Guide 编写了如何" -"使用 VMBuilder 创建 Ubuntu 镜像。" - -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 "" -" -X 参数传递给 ssh 将启用 ssh X11转发。如果不能工作，尝" -"试用 -Y 参数。" - -msgid "" -"The -d3 flag tells Oz to show status information as it " -"runs." -msgstr " -d3 参数指定 Oz 运行时显示状态信息。" - -msgid "" -"The -f format flag is " -"optional. If omitted, will try to infer the image format." -msgstr "" -" -f format参数是可选的，如果忽" -"略，将尝试推断镜像格式。" - -msgid "" -"The -u tells Oz to do the customization (install extra " -"packages, run the commands) once it does the initial install." -msgstr "" -" -u 参数指定 Oz 完成安装后运行自定义的安装动作（安装扩展" -"包，运行其他命令等）" - -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 "" -" -x <filename> 参数指定 Oz 输出给libvirt使用的 XML " -"文件名（否则它默认文件名是诸如 centos64Apr_03_2013-12:39:42这种名称）。" - -msgid "" -"The cloud-init package automatically fetches the public " -"key from the metadata server and places the key in an account." -msgstr "" -"cloud-init 自动从元数据服务器获取公钥并保存到账户内。" - -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 "" -"cloud-init 软件从元数据服务自动获取公钥并存放在账户内。不" -"同发行版的账户不一样。基于 Ubuntu 系的虚拟机，账户是 ubuntu 。Fedora 系的虚拟机，账户是 ec2-user。" - -msgid "" -"The command can do conversion between multiple formats, " -"including qcow2, qed, raw, vdi, vhd, and vmdk." -msgstr "" -" 命令可以转换多种格式的镜像文件，包括qcow2, qed, raw, vdi, " -"vhd, and vmdk.。" - -msgid "" -"The program is a tool from the libguestfs project that allows you to modify the " -"files inside of a virtual machine image." -msgstr "" -"程序是 libguestfs 项目的一个工具，它使你可以修改虚拟机镜像里的文件。" - -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 "" -" 脚本将在虚拟机启动的时候搜寻元数据服务获取公钥。公钥将会放在" -"镜像默认用户内。" - -msgid "" -"The cloud-init package " -"automatically fetches the public key from the metadata server and places the " -"key in an account. You can install cloud-init inside the CentOS guest by adding the EPEL repo:" -msgstr "" -" cloud-init 包自动从元数据服务获取" -"公钥并保存到账户，你可以在 CentOS虚拟机添加 EPEL 安装源来安装 cloud-init 包。" - -msgid "The CentOS project maintains official images for direct download." -msgstr "CentOS 项目维护官方的镜像下载。" - -msgid "" -"The Fedora project maintains a list of official cloud images at . " -msgstr "" -"Fedora 项目维护了一个官方云镜像列表，地址是 . " - -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 "" -"目前，镜像服务以及 OpenStack 的其他项目都不支持解析容器格式，如果你不确定你虚" -"拟机镜像容器格式，你可以安全的指定bare作为容器格式。" - -msgid "" -"The KVM hypervisor starts the virtual machine with the libvirt name, " -"centos-6.4, with 1024MB 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 10GB 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 "" -"KVM 虚拟化使用 centos-6.4 名称，1024MB内存启动虚拟机。虚拟" -"机还有一个关联文件/data/CentOS-6.4-x86_64-netinstall.iso 的虚拟的 CD-ROM，并" -"拥有 10GB 的qcow2格式的硬盘，硬盘文件位置在 /data/centos-6.4.qcow2。虚拟机配" -"置了网络使用 libvirt 的默认网络。且 VNC 服务监听所有的网卡，并且 libvirt 不会" -"自动启动 VNC 客户端也不会显示字符界面控制台（--no-autoconsole）。最后，" -"libvirt 将尝试以RHEL 6.x 发行版来优化虚拟机配置。" - -msgid "" -"The Ubuntu installer will ask how you want to manage upgrades on your " -"system. This option depends on your specific use case. If your virtual " -"machine instances will be connected to the Internet, we recommend \"Install " -"security updates automatically\"." -msgstr "" -"Ubuntu 安装程序询问你如何设置系统更新。这个选项依赖于你的使用环境，如果将来创" -"建的虚拟机能链接到因特网，我们推荐 \"Install security updates automatically" -"\"。" - -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 "" -"不同的发行版保存的账户不同，在基于 Ubuntu 的虚拟机，账户是 ubuntu ，基于 Fedora 的虚拟机，账户是 ec2-user 。" - -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 "" -"不同的发行版保存的账户不同，在基于 Ubuntu 的虚拟机，账户是 ubuntu ，基于 Fedora 的虚拟机，账户是 ec2-user 。" - -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 "镜像容器格式表示包含虚拟机镜像的文件是否也包含虚拟机的metadata数据。" - -msgid "" -"The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 " -"support is enabled with DHCP, which is the default." -msgstr "" -"默认的 TCP/IP 就OK了，尤其是，确认 IPv4 支持项启用了 DHCP，默认是启用的。" - -msgid "The default mirror proposed by the installer should be fine." -msgstr "选择默认的镜像站点即可。" - -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 "" -"虚拟机的磁盘格式指的是底层的磁盘镜像格式，虚拟设备厂商有不同的格式来放置虚拟" -"机磁盘镜像包含的信息。" - -msgid "" -"The disk is not detected by default by the Windows installer. When requested " -"to choose an installation target, click Load driver " -"and browse the file system to select the E:\\WIN8\\AMD64 folder. The Windows installer displays a list of drivers to " -"install. Select the VirtIO SCSI and network drivers, and continue the " -"installation." -msgstr "" -"Windows 安装程序默认不识别硬盘，当安装程序要求你选择安装位置时，点击" -"加载驱动并浏览文件系统选择 E:\\WIN8\\AMD64 文件夹。Windows 安装程序显示驱动列表，选择VirtIO SCSI和网络驱动，继" -"续安装。" - -msgid "The disk on the image has only one partition." -msgstr "镜像的磁盘只有一个分区。" - -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 "" -"支持这个功能的最简单的办法是安装 cloud-init 软件包到你的镜" -"像，它默认配置为将用户数据视为可执行脚本并且设置主机名。" - -msgid "The file system for the image fills the original size of the image." -msgstr "镜像的文件系统填充满镜像的原始大小。" - -msgid "The file system on the one partition is ext3 or ext4." -msgstr "仅有的分区文件系统是 ext3 或者　ext4 ." - -msgid "The following command uses the minimum amount of RAM, which is 256MB:" -msgstr "下面的命令使用最小内存，即256MB：" - -msgid "" -"The following example shows how to use the command to " -"create an empty image file, and command to start up a " -"virtual machine using that image file. As root:" -msgstr "" -"以下示例展示了如何使用 命令创建空镜像文件 " -"命令使用创建的空镜像文件启动虚拟机。以 root 用户执行：" - -msgid "" -"The following figure shows a completed partition table with a 1GB virtual " -"disk:" -msgstr "下图显示1GB虚拟磁盘分完区后的分区表：" - -msgid "" -"The installer may ask you to choose a host name. The default " -"(localhost.localdomain) is fine. You install the " -"cloud-init package later, which " -"sets the host name on boot when a new instance is provisioned using this " -"image." -msgstr "" -"安装程序让你输入主机名称，默的认(localhost.localdomain) 也" -"可以，随后你将安装 cloud-init 包，" -"它将在镜像将来启动时设置主机名。" - -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 "" -"安装程序要求填入主机名。默认的 (ubuntu) 即可。后面我们将安" -"装 cloud-init 包，cloud-init 包将在将来使用镜像创建新虚拟机启动的时候设置主机" -"名。" - -msgid "" -"The minimum supported disk size for FreeBSD is 1GB. Because the goal is to " -"make the smallest possible base image, the example uses that minimum size. " -"This size is sufficient to include the optional doc, games, and lib32 " -"collections. To include the ports collection, add another 1GB. To include " -"src, add 512MB." -msgstr "" -"FreeBSD 支持的最小磁盘大小是1GB。因为我们的目标是建立一个最小化的基础镜像文" -"件，所以示例使用的最小磁盘大小，足够容纳可选的文档，游戏以及lib32库。要包含" -"ports软件，需要添加额外的1GB空间，要包含源码，再添加512M空间。" - -msgid "" -"The name of your virtual machine image is centos-6.4; you " -"need this name when you use commands to manipulate the " -"state of the image." -msgstr "" -"你的虚拟机名称是 centos-6.4；在你使用 命" -"令操作虚拟机状态的时候你需要使用这个名称。" - -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 "" -"操作系统会在/etc/sysconfig/network-scripts/ifcfg-eth0 " -"和 /etc/udev/rules.d/70-persistent-net.rules 这类文件记" -"录下网卡MAC地址，但是，虚拟机的网卡MAC地址在每次虚拟机创建的时候都会不同，因" -"此这些信息必须从配置文件删除掉。" - -msgid "" -"The operating system records the MAC address of the virtual Ethernet card in " -"locations such as /etc/udev/rules.d/70-persistent-net.rules during the installation process. However, each time the image " -"boots up, the virtual Ethernet card will have a different MAC address, so " -"this information must be deleted from the configuration file." -msgstr "" -"操作系统会在/etc/sysconfig/network-scripts/ifcfg-eth0 " -"和 /etc/udev/rules.d/70-persistent-net.rules 这类文件记" -"录下网卡MAC地址，但是，虚拟机的网卡MAC地址在每次虚拟机创建的时候都会不同，因" -"此这些信息必须从配置文件删除掉。" - -msgid "" -"The partition table for the image describes the original size of the image." -msgstr "镜像的分区表表述的是镜像的原始大小。" - -msgid "" -"The previous script only gets the ssh public key from the metadata server. " -"It does not get user data, which is optional data that can be passed by the " -"user when requesting a new instance. User data is often used to run a custom " -"script when an instance boots." -msgstr "" -"前面的脚本仅仅只是从元数据服务获取了 ssh 的公钥，并未获取用户数据，用户数据是" -"用户申请新虚拟机可以传递到虚拟机内的可选数据，通常用于在虚拟机启动时做一些定" -"制化工作。" - -msgid "" -"The simplest way to obtain a virtual machine image that works with OpenStack " -"is to download one that someone else has already created. Most of the images " -"contain the cloud-init package to " -"support SSH key pair and user data injection. Because many of the images " -"disable SSH password authentication by default, boot the image with an " -"injected key pair. You can SSH into the instance with the private key and " -"default login account. See the OpenStack End User Guide for more information on how to " -"create and inject key pairs with OpenStack." -msgstr "" -"获取 OpenStack 兼容的虚拟机镜像的最简单的方法就是直接下载已经制作好的镜像，大" -"多数镜像中包含 cloud-init 软件包以" -"支持 SSH 密钥对以及用户数据注入。由于许多镜像默认禁用了SSH 密码认证，镜像首次" -"启动是会注入SSH 密钥对。你可以使用默认账户的私钥登陆到创建的虚拟机中。参考" -"OpenStack 使用指南" -" 获取如何创建和注入密钥对到Openstack的详细信息。" - -msgid "The simplest way to support this is to install in your image the:" -msgstr "实现以上操作最简单的方法是安装以下软件到镜像内：" - -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 5GB 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 10GB. When the disk for an instance is resized up, " -"zeros are just added to the end." -msgstr "" -"镜像磁盘的大小在最开始创建磁盘的时候就已经决定了的，然而，OpenStack 通过指定" -"不同的硬件配置规格让你启动磁盘大小不同的虚拟机。例如，如果你的镜像是5GB，你创" -"建的虚拟机指定的虚拟机规格是 m1.small 。最终创建的虚拟机的系统磁盘是10GB。当" -"虚拟机的磁盘扩充的时候，在磁盘的后面以0填充。" - -msgid "" -"The typical way that users access virtual machines running on OpenStack is " -"to ssh using public key authentication. For this to work, your virtual " -"machine image must be configured to download the ssh public key from the " -"OpenStack metadata service or config drive, at boot time." -msgstr "" -"访问在 OpenStack 内运行的虚拟机典型的办法是通过 ssh 使用公钥认证。为了实现这" -"个，你的虚拟机镜像必须被配置为在虚拟机启动时能从 OpenStack 元数据服务获取ssh " -"公钥或者使用config 磁盘。" - -msgid "" -"The underlying image file that you created with is ready to " -"be uploaded. For example, you can upload the /tmp/centos-6.4." -"qcow2 image to the Image service." -msgstr "" -"前面你使用 命令创建的镜像已经准备好可以上传了，例如，你可以" -"上传 /tmp/centos-6.4.qcow2 文件到镜像服务。" - -msgid "" -"The underlying image file that you created with , such as " -"/tmp/trusty.qcow2, is now ready for uploading to the " -"OpenStack Image service." -msgstr "" -"前面你使用 命令创建的镜像已经准备好可以上传了，你可以上传 " -"/tmp/trusty.qcow2 文件到 Openstack 镜像服务。" - -msgid "" -"The underlying image file that you created with qemu-img create is ready to " -"be uploaded to the Image service." -msgstr "以上步骤你使用 qemu-img 创建的镜像文件已经完备，可以上传到镜像服务了。" - -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 "" -"Microsoft Server 2012 中的 Hyper-V 版本使用的新的 VHDX 格式，它比" -"VHD有额外的新的特性例如支持更大的磁盘以及意外掉电时数据丢失保护。" - -msgid "" -"The virtualized CMOS almost always stores its time in UTC, so unless you " -"know otherwise, select UTC." -msgstr "虚拟的CMOS始终存储它的时间时区为UTC,除非你知道原因，否则选择UTC." - -msgid "Then, during the boot process, you must:" -msgstr "然后，在启动过程中，你必须：" - -msgid "" -"There are different options for partitioning the disks. The default " -"installation uses LVM partitions, and creates three partitions (/" -"boot, /, swap), which works fine. " -"Alternatively, you might want to create a single ext4 partition that is " -"mounted to \"/\", which also works fine." -msgstr "" -"磁盘分区有好几个选项，默认使用LVM分区，会创建(/boot, " -"/, swap)三个分区，默认设置就可以正常工作。另外你也可以只" -"建立一个 ext4 分区挂载到 \"/\"，这也可以正常工作。 " - -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 "" -"目前有几个分区选项。默认的安装程序使用 LVM 分区，将创建三个分区 (/" -"boot, /, swap)，使用默认的即可。作为可选的，" -"你也可以创建单个 ext4 分区，挂载 \"/\"。" - -msgid "There are several tools that are designed to automate image creation." -msgstr "有几个工具设计为自动创建镜像。" - -msgid "" -"There is a known bug in Ubuntu 14.04; when you select \"Continue\", the " -"virtual machine will shut down, even though it says it will reboot." -msgstr "" -"在 Ubuntu 14.04中有一个已知bug；当你选择 \"Continue\"， 虚拟机将关机，即使它" -"显示它将重启。" - -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 "" -"目前有 工具可以完成清理虚拟机镜像内的 MAC 地址相关的信息。" - -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 "" -"guestfish有大量庞大的功能，完全介绍它查出了本文档的功能范围。因此，我们推荐你" -"阅读 guestfs-recipes 文档页面感知通过这些工具都能做什么。" - -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 "" -"因此，如果你使用 Xen ，我们推荐当你创建镜像时，只建立一个 ext3 或者 ext4 分区" -"（而且没有LVM管理）。否则，继续往下看。" - -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 "" -"Oz 模板指定了 Centos 6.4 安装 ISO 的下载位置。 Oz 使用版本信息确认了使用哪一" -"个 kickstart 文件。在这个示例中，是 RHEL6.auto 。它添加 " -"EPEL 软件库，并且安装在 packages 字段指定的 epel-" -"release, cloud-utils, 以及 cloud-init 包。" - -msgid "This VM must also have Internet access to download packages." -msgstr "虚拟机必须能访问 Internet 以便下载软件包。" - -msgid "" -"This example creates a Windows Server 2012 qcow2 image, using and the KVM hypervisor." -msgstr "" -"这个例子创建一个Windows Server 2012 qcow2镜像，使用以及KVM虚" -"拟化。" - -msgid "" -"This example creates a generic, bootable Ubuntu image of the latest release." -msgstr "这个示例创建了一个通用的，可启动的最新版本 Ubuntu 镜像。" - -msgid "" -"This example creates a minimal FreeBSD image that is compatible with " -"OpenStack and bsd-cloudinit. The bsd-" -"cloudinit program is independently maintained and in active " -"development. The best source of information on the current state of the " -"project is at http://pellaeon.github.io/bsd-cloudinit/." -msgstr "" -"这个示例创建了一个兼容 OpenStack 以及 bsd-cloudinit的最小化的 FreeBSD 镜像。bsd-cloudinit 是一个独立维护并且正在积极开发中的程序。项目当前的源码信息状态站" -"点是 http://" -"pellaeon.github.io/bsd-cloudinit/。" - -msgid "" -"This example creates the image as before, but for arm architecture. More " -"elements are available in the git source directory and documented in the diskimage-builder elements " -"documentation." -msgstr "" -"这个示例使用之前创建的镜像，但是针对 ARM 结构，更多的基础元素参见 git 源目录 且文档参考 镜像生成器基础元素" -"文档。 " - -msgid "" -"This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image " -"for a different version of Ubuntu, follow these steps with the noted " -"differences." -msgstr "" -"这个示例安装Ubuntu 14.04 (Trusty Tahr) 版本镜像。创建其他版本的Ubuntu镜像，注" -"意下面安装过程的标记不同的地方。" - -msgid "" -"This example shows how to create a FreeBSD 10 image. To create a FreeBSD 9.2 " -"image, follow these steps with the noted differences." -msgstr "" -"这个示例显示了如何创建 FreeBSD 10 镜像，要创建 FreeBSD 9.2 镜像，注意以下步骤" -"中提示。" - -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 "" -"这个示例演示了如何使用修改文件，这个命令既可以通过使用" -"-a标记后跟文件名作为参数，也可以通过使用-d后跟虚拟机的 domain 名称作为参数。下面的示例演示如何修改在libvirt中运" -"行的 domain 名称为 instance-000000e1的虚拟机内/" -"etc/shadow文件：" - -msgid "" -"This example shows you how to install a CentOS image and focuses mainly on " -"CentOS 6.4. Because the CentOS installation process might differ across " -"versions, the installation steps might differ if you use a different version " -"of CentOS." -msgstr "" -"这个示例演示如何安装 CentOS 镜像，主要是 CentOS 6.4。由于不同版本的 CentOS 安" -"装过程稍有差别，因此其他版本安装过程可能和示例中有不一样的地方。" - -msgid "" -"This example will convert a raw image file named centos7.img to a qcow2 image file." -msgstr "" -"这个示例将转换换一个裸格式镜像文件 centos7.img 到qcow2镜" -"像文件。" - -msgid "" -"This guide describes how to obtain, create, and modify virtual machine " -"images that are compatible with OpenStack." -msgstr "这个指南描述了如何获取，创建以及修改 OpenStack 兼容的虚拟机镜像。" - -msgid "This is a virtual machine image in raw format, as described above." -msgstr "裸格式镜像，如前面描述。" - -msgid "" -"This menu enables you to update previous settings. Check that the settings " -"are correct, and click exit." -msgstr "" -"这个菜单让你更新之前的设置，检查参数是否正确，然后选择 exit。" - -msgid "" -"This sets console output to go to the serial console, which is displayed by " -", and the video console for sites with VNC or Spice " -"configured." -msgstr "" -"设置console输出到串口控制台，可以由 查看，以及图形console使" -"用 VNC 或者 Spice 。" - -msgid "" -"This starts a guestfish session. Note that the guestfish prompt looks like a " -"fish: > <fs>." -msgstr "" -"通过上面命令，进入了 guestfish 会话，注意 guestfish提示符像一条鱼的样子： " -"> <fs>." - -msgid "This will launch a VM and start the installation process." -msgstr "这将启动一个虚拟机并且开始安装过程。" - -msgid "" -"To allow Cloudbase-Init to run scripts during an " -"instance boot, set the PowerShell execution policy to be unrestricted:" -msgstr "" -"为了让Cloudbase-Init在系统启动时运行脚本，设置" -"PowerShell执行策略解除限制。" - -msgid "To build an image, call the following script:" -msgstr "要创建镜像，输入以下命令：" - -msgid "To create a FreeBSD image" -msgstr "创建 FreeBSD 镜像" - -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 or VirtualBox), you can use that instead and " -"just convert the file to raw once you are done." -msgstr "" -"要创建新的虚拟机镜像，你需要虚拟机系统的安装 CD 或 DVD ISO 文件。你还需要虚拟" -"化工具，你可以使用KVM。或者如果你有图形的桌面虚拟化工具（例如， VMware " -"Fusion 或者 VirtualBox），你可以使用它替代KVM，只是在你完成后需要转换镜像格式" -"为裸格式。" - -msgid "" -"To eject a disk by using the command, libvirt requires that " -"you attach an empty disk at the same target that the CDROM was previously " -"attached, which should be hdc. You can confirm the " -"appropriate target using the command." -msgstr "" -"使用 卸载磁盘，libvirt需要挂接一个空磁盘到之前挂接CDROM的地" -"方，设备名应该是 hdc。可以使用 命令来确" -"认。" - -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 "" -"使用 弹出光驱时，libvirt 要求你挂一个空磁盘在光驱相同的位" -"置。在之前盘符是 hdc 。你可以使用 命令来" -"完成。" - -msgid "" -"To enable the hypervisor to reboot or shutdown an instance, you must install " -"and run the acpid service on the " -"guest system." -msgstr "" -"为了让虚拟化层能重启和关闭虚拟机，必须在虚拟机内安装并运行 acpid 服务。" - -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 "" -"要获取 ssh 公钥并存放到 root 账户。编辑 /etc/rc.local " -"文件并添加以下内容到 \"touch /var/lock/subsys/local\" 这行之前。下面的脚本片" -"段来自 rackerjoe oz-image-build CentOS 6 " -"template。" - -msgid "" -"To install the operating system, complete the following steps inside the VM:" -msgstr "在虚拟机里，完成以下步骤安装操作系统：" - -msgid "" -"To keep things brief, we'll sometimes use the term \"image\" instead of " -"\"virtual machine image\"." -msgstr "为了简化，有时文档使用 \"镜像\" 代替 \"虚拟机镜像\" 。" - -msgid "To run this:" -msgstr "运行：" - -msgid "" -"To see how the settings affect the deletion of a running instance, check the " -"directory where the images are stored:" -msgstr "查看以上设置对被删除的虚拟机镜像文件的影响，查看以下目录：" - -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 "" -"运行 命令设置镜像 cloud-init 软件包使用" -"的元数据源。当屏幕出现提示时，选择 EC2 数据源。" - -msgid "" -"To verify that the libvirt \"default\" network is enabled, use the " -" command and verify that the \"default\" network is active:" -msgstr "" -"检查 \"default\" 默认网络是否激活，使用 命令并查看 " -"\"default\" 网络是否是启用状态。" - -msgid "Tool support for image creation" -msgstr "支持创建镜像的工具" - -msgid "UEC tarball" -msgstr "UEC tarball" - -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 "" -"Ubuntu 企业云是基于OpenStack 的云基础结构 ，之前是已经中断的基于桉树云的解决" -"方案。" - -msgid "" -"Undefine the domain since you no longer need to have this virtual machine " -"image managed by libvirt:" -msgstr "" -"将虚拟机domain undefine掉，以为你已经完成镜像制作不再需要libvirt进行管理。" - -msgid "Undefine the libvirt domain" -msgstr "删除 libvirt 虚拟机域" - -msgid "Use cloud-init to fetch the public key" -msgstr "使用 cloud-init 获取公钥" - -msgid "" -"Use or to connect to the VM and start the " -"Windows installation." -msgstr "" -"使用 或 命令连接到虚拟机开始 Windows 安" -"装。" - -msgid "Use cloud-init to fetch the public key" -msgstr "使用 cloud-init 获取公钥" - -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 "" -"使用 nova.conf的选项来控制在 /var/lib/nova/" -"instances/_base/ 目录中是否保存或者多长时间，未使用的基础镜像。如" -"果你配置了虚拟机活迁移。所有的计算节点还需要共享同一个 /var/lib/" -"nova/instances/ 目录" - -msgid "" -"Use the virt-sysprep utility. This performs various " -"cleanup tasks such as removing the MAC address references. It will clean up " -"a virtual machine image in place:" -msgstr "" -"使用 virt-sysprep 工具，它将通过几个步骤完成清除镜像内相关" -"记录的MAC地址信息，" - -msgid "Use the command to get the VNC port number." -msgstr "使用 命令获取 VNC 端口号。" - -msgid "Use the virt-manager X11 GUI" -msgstr "使用 virt-manager X11 图形界面" - -msgid "Use virt-install and connect by using a local VNC client" -msgstr "使用 virt-install 且使用本地 VNC 客户端连接" - -msgid "Username: Administrator" -msgstr "用户名： Administrator" - -msgid "Using sparse representation, so the image size is smaller." -msgstr "使用稀疏文件呈现方式，因此镜像尺寸更小。" - -msgid "VBoxManage: VDI (VirtualBox) to raw" -msgstr "VBoxManage: VDI (VirtualBox) 转换为 raw" - -msgid "VDI" -msgstr "VDI" - -msgid "VDI (VirtualBox)" -msgstr "VDI (VirtualBox)" - -msgid "VHD" -msgstr "VHD" - -msgid "VHD (Hyper-V)" -msgstr "VHD (Hyper-V)" - -msgid "VHDX" -msgstr "VHDX" - -msgid "VM Image Guide" -msgstr "虚拟机镜像指南" - -msgid "VMBuilder" -msgstr "VMBuilder" - -msgid "VMDK" -msgstr "VMDK" - -msgid "VMDK (VMware)" -msgstr "VMDK (VMware)" - -msgid "" -"VMware's ESXi hypervisor uses the VMDK (Virtual Machine " -"Disk) format for images." -msgstr "" -"VMDK (Virtual Machine Disk) 是 VMware ESXi 虚拟化使用的镜像格" -"式。" - -msgid "VeeWee" -msgstr "VeeWee" - -msgid "Verify the libvirt default network is running" -msgstr "检查 libvirt 默认网络是否运行" - -msgid "" -"Virtual machine images come in different formats, some of which are " -"described below." -msgstr "虚拟机镜像有不同的格式，下面具体列出。" - -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 "" -" VDI (Virtual Disk Image)是 VirtualBox 使用的镜像格式。" -"OpenStack 计算节点并不直接支持VDI格式，因此你在OpenStack中使用VDI镜像需要提前" -"转换成其他受支持的格式。" - -msgid "Volume-from-Image properties" -msgstr "镜像转换的卷属性" - -msgid "Wait for the machine shutdown." -msgstr "等待虚机关闭。" - -msgid "" -"We don't recommend creating raw images by dd'ing block device files, we " -"discuss how to create raw images later." -msgstr "" -"我们不推荐使用dd块设备的方法创建裸格式镜像，我们将在后面讨论如何创建裸格式镜" -"像。" - -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 "" -"在做任何操作之前，必须先在 guestfish提示符运行命令。它会启动" -"一个虚拟机，用于完成我们所以的对文件的操作。通过" -"命令，我们可查看镜像内的文件系统列表：我们必" -"须挂载包含根分区的那个逻辑卷：" - -msgid "" -"We're done, so we can exit using the command:" -msgstr "" -"一切都完成后，我们可以使用 命令退出guestfish提示符：" -"" - -msgid "Web site name: mirror.umd.edu" -msgstr "网站地址：mirror.umd.edu" - -msgid "What is a virtual machine image?" -msgstr "虚拟机镜像是什么？" - -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 "" -"在创建 Ubuntu 镜像时， 必须明确的配置元数据源。OpenStack 元数" -"据服务仿效 Amazon EC2 元数据服务。" - -msgid "" -"When converting an image file with Windows OS, ensure the virtio driver is " -"installed. Otherwise, you will get a blue screen of death or BSOD when " -"launching the image due to lack of the virtio driver. Another option is to " -"set the image properties as below when you update the image in glance to " -"avoid this issue, but it will reduce performance significantly." -msgstr "" -"当转换一个Windows系统的镜像文件时，需确保镜像内系统已安装好virtio驱动。否则，" -"在你启动虚拟机时会由于缺少virtio驱动遇到蓝屏死机。另外避免这个问题的方法是按" -"如下命令通过更新glance服务中镜像属性，但是这个方法会明显的降低磁盘性能。" - -msgid "" -"When creating Block Storage volumes from images, also consider your " -"configured image properties. If you alter the core image properties, you " -"should also update your Block Storage configuration. Amend " -"in the /etc/cinder/cinder.conf file on all controller " -"nodes to match the core properties you have set in the Image service." -msgstr "" -"当从镜像创建块存储卷的时候，需要考虑镜像的属性。如果你修改镜像的核心属性，你" -"也应该更新块存储配置。修改所有匹配你设置在镜像服务的核心属性的控制节点 的" -"/etc/cinder/cinder.conf 文件的 值。" - -msgid "" -"When prompted about the optional doc, games, lib32, ports, and " -"src system components, select only those that you need. " -"It is possible to have a fully functional installation without selecting " -"additional components selected. As noted previously, a minimal system with a " -"1GB virtual disk supports doc, games, and lib32 inclusive. The ports " -"collection requires at least 1GB additional space and possibly more if you " -"plan to install many ports. The src collection requires an additional 512MB." -msgstr "" -"当提示可选doc, games, lib32, ports, and src 系统组件时，选" -"择你需要的组件，当你不选可选的系统组件时也可以完成一个完全功能安装，如前提" -"示，最小化系统的1GB虚拟磁盘支持包含doc, games, and lib32内容。要包含ports 软" -"件组需要至少1GB额外空间，如果你计划安装更多port软件时还需要更多的空间，" -"src（源代码）组需要额外512MB空间。" - -msgid "" -"When prompted, choose to run the ISO in Install mode." -msgstr "当出现提示的时候，选择运行ISO 于 Install 模式。" - -msgid "" -"When the installation has completed, the Congratulations, your " -"CentOS installation is complete screen appears." -msgstr "" -"安装完成后，屏幕出现 Congratulations, your CentOS installation is " -"complete 界面。" - -msgid "" -"When the installation is done, in the Complete the Cloudbase-Init " -"Setup Wizard window, select the Run Sysprep " -"and Shutdown check boxes and click Finish." -msgstr "" -"当安装完成后，在Complete the Cloudbase-Init Setup Wizard 窗口，选择Run Sysprep和Shutdown 复选框，然后点击Finish。" - -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 "" -"使用 qcow2 格式镜像你应该勾选 'customize before install'，然后跳转到磁盘属性" -"并且确保明确选择了qcow2格式。这将保证虚拟机磁盘大小正确。" - -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 "" -"当使用 libvirt default 默认网络时，libvirt 将连接虚拟机" -"到 virbr0 网桥。libvirt管理下的 dnsmasq 进程将处理 " -"192.168.122.0/24 子网上的 IP地址。且 libvirt 有 iptables 规则负责这个子网 " -"NAT 转发。" - -msgid "" -"When you add an image to the Image service, you can specify its disk and " -"container formats." -msgstr "当你添加镜像到镜像服务，你可以指定镜像的磁盘和容器格式。" - -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 "" -"当你安装后首次启动时，虚拟机将会询问你认证工具，你只需要选择 'Exit'。然后使用" -"你设置的root密码以root用户登录。" - -msgid "" -"When you boot for the first time after installation, you might be prompted " -"about authentication tools. Select Exit. Then, log in " -"as root." -msgstr "" -"安装后的第一次启动，会提示认证工具（我咋没遇到过啊，文档bug吧）。选择" -"Exit。然后，以root用户登录。" - -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 "" -"当创建 Linux 镜像时，你必须决定如何分区。选择不同的分区方法会对重新调整分区大" -"小有不同的影响，请看以下章节的描述。" - -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 "" -"当你创建虚拟机镜像的时候，你需要连接到虚拟化层的图形控制台，图形控制台作为虚" -"拟机的显示器并且使你能使用键盘和鼠标和虚拟机操作系统安装程序进行交互。KVM 通" -"过 VNC （虚拟网络计算）协议或者更新的 SPICE 协议来完成图形控制台的显示。这里我们使用VNC，因此你" -"将在你的本地桌面更加可能使用 VNC 客户端。" - -msgid "When you're done, clean up:" -msgstr "一切操作完成后，清理命令：" - -msgid "When you're done, clean up:" -msgstr "完成后，清理命令： " - -msgid "" -"With these packages installed, the image performs the root partition resize " -"on boot. For example, in the /etc/rc.local file. These " -"packages are in the Ubuntu and Debian package repository, as well as the " -"EPEL repository (for Fedora/RHEL/CentOS/Scientific Linux guests)." -msgstr "" -"通过安装这些包，镜像在启动时完成root分区改变大小。例如，通过设置/" -"etc/rc.local 文件，这些包包在Ubuntu 和 Debian 包管理库内以及 EPEL " -"库（ Fedora/RHEL/CentOS/Scientific 系列 Linux）" - -msgid "Write a custom script to fetch the public key" -msgstr "编写脚本获取公钥" - -msgid "Write a script to fetch the public key (if no cloud-init)" -msgstr "编写脚本获取公钥（如果未使用cloud-init）" - -msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" -msgstr "Xen: 单一 ext3/ext4 分区 ( 无LVM , 无 /boot ,无swap分区区 )" - -msgid "" -"You can access this information through the metadata service or referring to " -"Store metadata on the configuration drive. As the OpenStack " -"metadata service is compatible with version 2009-04-04 of the Amazon EC2 " -"metadata service, consult the Amazon EC2 documentation on Using Instance Metadata for details on " -"how to retrieve user data." -msgstr "" -"你可以通过元数据服务访问这些信息或者参考 在配置驱动器存储元数据。Openstack 元数据服务兼容亚马逊 EC2 元数据服务标准 2009-04-04 版。查阅" -"亚马逊 EC2 文档 使用虚机元数据" -"获取如何获取用户数据的详细信息。" - -msgid "" -"You can add metadata to Image service images by using the --" -"property key=value parameter with the or command. " -"More than one property can be specified. For example:" -msgstr "" -"你可以使用 或者 命令设置 --" -"property key=value 添加元数据到镜像服务中的镜像。多个属性值可指定。例如：" - -msgid "" -"You can also use the GUI to detach and reboot it by manually stopping and " -"starting." -msgstr "你也可以使用图形界面手工停止和启动虚拟机来完成以上功能。" - -msgid "" -"You can change the name of the account used by cloud-init " -"by editing the /etc/cloud/cloud.cfg file and adding a " -"line with a different user. For example, to configure cloud-init to put the key in an account named admin, add this line to the " -"configuration file:" -msgstr "" -"你可以编辑 /etc/cloud/cloud.cfg 文件添加一行修改 " -"cloud-init 使用的账户名，例如，添加以下这行到配置文件，来" -"配置 cloud-init 存放公钥到admin账户。" - -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 "" -"你可以编辑 /etc/cloud/cloud.cfg 文件添加一行修改 " -"cloud-init 使用的账户名，例如，添加以下这行到配置文件，来" -"配置 cloud-init 存放公钥到admin账户：" - -msgid "" -"You can change the name of the account used by cloud-init by editing the /etc/cloud/cloud.cfg file and adding a line with a different user. For example, to " -"configure cloud-init to put the " -"key in an account named admin, add this line to the " -"configuration file:" -msgstr "" -"你可以编辑 /etc/cloud/cloud.cfg 文件添加一行修改 " -"cloud-init 使用的账户名，例如，添加以下这行到配置文件，来" -"配置 cloud-init 存放公钥到 admin 账户。" - -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 "" -"你可以编辑 /etc/cloud/cloud.cfg 文件添加一行修改 " -"cloud-init 使用的账户名，例如，添加以下这行到配置文件，来" -"配置 cloud-init 存放公钥到admin账户。" - -msgid "" -"You can set the container format for your image to one of the following " -"values:" -msgstr "你可设置你的镜像容器格式为以下之一：" - -msgid "" -"You can specify up to 1GB additional RAM to make the installation process " -"run faster." -msgstr "你可以指定最大1GB内存让安装程序运行更快。" - -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 "" -"你无须 /boot分区，除非你的镜像使用的是较老的 Linux 发行" -"版，那些发行版要求 /boot 目录不能被 LVM管理。" - -msgid "" -"You do not need to add users at this time. The bsd-cloudinit program adds a freebsd user account if one " -"does not exist. The ssh keys for " -"this user are associated with OpenStack. To customize this user account, you " -"can create it now. For example, you might want to customize the shell for " -"the user." -msgstr "" -"你当前不需要添加用户，如果 freebsd 账户不存在， " -"bsd-cloudinit 程序会添加一个 freebsd 用户账户。用户的ssh 秘钥" -"和OpenStack相关联。要定制用户，你可以现在创建，例如，你可能想定制用户的" -"shell。" - -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 "" -"你必须配置镜像以便镜像内核输出启动日志到 ttyS0 设备，尤其" -"是 console=ttyS0参数必须在启动时传递给内核。" - -msgid "You must configure these items for your image:" -msgstr "你的镜像必须满足以下配置：" - -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 "" -"在镜像内你必须安装 SSH 服务并且确保它在启动时自动启动，否则你不能通过 ssh 连" -"接到你在 OpenStack 内的虚拟机。ssh 服务包名通常叫做 openssh-server 。" - -msgid "" -"You must remove the network persistence rules in the image because they " -"cause the network interface in the instance to come up as an interface other " -"than eth0. This is because your image has a record of the MAC address of the " -"network interface card when it was first installed, and this MAC address is " -"different each time the instance boots. You should alter the following files:" -msgstr "" -"你必须删除镜像内网络规则文件，因为它这会导致新创建虚拟机启动时网卡不是eth0。" -"这是由于你创建的镜像第一次安装时会记录网卡的MAC地址。并且MAC地址在每次创建虚" -"拟机时不同。你应该修改以下文件：" - -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 "" -"你需要加载 nbd （网络块设备）内核模块来挂载 qcow2 镜像文" -"件。下面将加载满足我们需求的支持16个块设备，以root用户执行：" - -msgid "" -"You now have a VM that boots from the downloaded install ISO and is " -"connected to the blank virtual disk that you created previously." -msgstr "" -"现在你的虚拟机从之前你下载的ISO文件启动并且使用了之前准备好的空白虚拟磁盘。" - -msgid "" -"You saved the netinstall ISO image to the /data/isos " -"directory." -msgstr "你保存下载的网络安装ISO镜像在 /data/isos 目录。" - -msgid "Your image is ready to upload to the Image service:" -msgstr "你的镜像已经准备好上传到镜像服务了：" - -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 "" -"你的镜像必须能在启动的时候重新伸缩大小以便匹配最终用户的需求。否则，在虚拟机" -"启动后，你需要手工改变分区的容量才能使用虚拟机指定的硬件配置规格的磁盘分容量" -"大于你镜像原有容量的那部分容量。" - -msgid "Your script must do something like the following:" -msgstr "你的脚本需要完成以下功能：" - -msgid "current" -msgstr "current" - -msgid "fedora-20" -msgstr "fedora-20" - -msgid "guestfish" -msgstr "guestfish" - -msgid "guestmount" -msgstr "guestmount" - -msgid "imagefactory" -msgstr "imagefactory" - -msgid "img-uuid" -msgstr "img-uuid" - -msgid "node-root" -msgstr "node-root" - -msgid "preallocate_images=none" -msgstr "preallocate_images=none" - -msgid "qcow2" -msgstr "qcow2" - -msgid "qed" -msgstr "qed" - -msgid "qemu-img convert: raw, qcow2, qed, vdi, vmdk, vhd" -msgstr "qemu-img 转换:raw, qcow2, qed, vdi, vmdk, vhd" - -msgid "qemu-img format strings" -msgstr "qemu-img 格式字符列表" - -msgid "raw" -msgstr "raw" - -msgid "remove_unused_base_images=True" -msgstr "remove_unused_base_images=True" - -msgid "remove_unused_original_minimum_age_seconds=86400" -msgstr "remove_unused_original_minimum_age_seconds=86400" - -msgid "remove_unused_resized_minimum_age_seconds=3600" -msgstr "remove_unused_resized_minimum_age_seconds=3600" - -msgid "sda6" -msgstr "sda6" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -msgid "translator-credits" -msgstr "translator-credits" - -msgid "vdi" -msgstr "vdi" - -msgid "vg00" -msgstr "vg00" - -msgid "virt-* tools" -msgstr "virt-* tools" - -msgid "vm-image" -msgstr "vm-image" - -msgid "vm-name" -msgstr "vm-name" - -msgid "vmdk" -msgstr "vmdk" - -msgid "vpc" -msgstr "vpc" diff --git a/doc/image-guide/pom.xml b/doc/image-guide/pom.xml deleted file mode 100644 index bc55b81082..0000000000 --- a/doc/image-guide/pom.xml +++ /dev/null @@ -1,81 +0,0 @@ - - - - org.openstack.docs - parent-pom - 1.0.0-SNAPSHOT - ../pom.xml - - 4.0.0 - openstack-image-guide - jar - OpenStack Virtual Machine Image Guide - - - local - 1 - - - - - - - - com.rackspace.cloud.api - clouddocs-maven-plugin - - - - generate-webhelp - - generate-webhelp - - generate-sources - - - ${comments.enabled} - os-image-guide - 1 - UA-17511903-1 - - appendix toc,title - article/appendix nop - article toc,title - book toc,title,figure,table,example,equation - chapter toc - section toc - part toc - preface toc - qandadiv toc - qandaset toc - reference toc,title - set toc,title - - - 0 - 0 - 1 - 1 - 0 - image-guide - image-guide - - - - - - true - . - - bk-imageguide.xml - - http://docs.openstack.org/image-guide/content - ${basedir}/../glossary/glossary-terms.xml - openstack - - - - - diff --git a/doc/image-guide/roadmap.rst b/doc/image-guide/roadmap.rst deleted file mode 100644 index d9961e7e8e..0000000000 --- a/doc/image-guide/roadmap.rst +++ /dev/null @@ -1,22 +0,0 @@ -Roadmap for Virtual Machine Image Guide ---------------------------------------- - -This file is stored with the source to offer ideas for what to work on. -Put your name next to a task if you want to work on it and put a WIP -review up on review.openstack.org. - -May 21, 2014 -To do tasks: - -- Add a chapter describing how to make an image for Database as a - Service (trove) -- Add audience information; who is this book intended for - -Ongoing tasks: - -- Ensure it meets conventions and standards - -Wishlist tasks: - -- Replace all individual client commands (like keystone, glance) with - openstack client commands diff --git a/doc/image-guide/section_centos-example.xml b/doc/image-guide/section_centos-example.xml deleted file mode 100644 index b160d6876d..0000000000 --- a/doc/image-guide/section_centos-example.xml +++ /dev/null @@ -1,332 +0,0 @@ - -
- Example: CentOS image - This example shows you how to install a CentOS image and focuses mainly on CentOS 6.4. - Because the CentOS installation process might differ across versions, the installation steps - might differ if you use a different version of CentOS. - - Download a CentOS install ISO - - Navigate to the CentOS - mirrors page. - - - Click one of the HTTP links in the right-hand column next to - one of the mirrors. - - - Click the folder link of the CentOS version that you want to use. For example, - 6.4/. - - - Click the isos/ folder link. - - - Click the x86_64/ folder link for 64-bit images. - - - Click the netinstall ISO image that you want to download. For example, - CentOS-6.4-x86_64-netinstall.iso is a good choice because - it is a smaller image that downloads missing packages from the Internet during - installation. - - - - Start the installation process - Start the installation process using either virt-manager or - virt-install as described in the previous section. If you use - virt-install, do not forget to connect your VNC client to the - virtual machine. - Assume that: - - - The name of your virtual machine image is centos-6.4; - you need this name when you use virsh commands to manipulate the - state of the image. - - - You saved the netinstall ISO image to the /data/isos directory. - - - If you use virt-install, the commands should look something like - this: - # qemu-img create -f qcow2 /tmp/centos-6.4.qcow2 10G -# virt-install --virt-type kvm --name centos-6.4 --ram 1024 \ ---disk /tmp/centos-6.4.qcow2,format=qcow2 \ ---network network=default \ ---graphics vnc,listen=0.0.0.0 --noautoconsole \ ---os-type=linux --os-variant=rhel6 \ ---extra-args="console=tty0 console=ttyS0,115200n8 serial" \ ---location=/data/isos/CentOS-6.4-x86_64-netinstall.iso - - - Step through the installation - At the initial Installer boot menu, choose the Install or upgrade an - existing system option. Step through the installation prompts. Accept the - defaults. - - - - - - - - - - - Configure TCP/IP - The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 support - is enabled with DHCP, which is the default. - - - - - - - - Point the installer to a CentOS web server - Choose URL as the installation method. - - - - - - Depending on the version of CentOS, the net installer requires the user to specify - either a URL or the web site and a CentOS directory that corresponds to one of the - CentOS mirrors. If the installer asks for a single URL, a valid URL might be - http://mirror.umd.edu/centos/6/os/x86_64. - - Consider using other mirrors as an alternative to - mirror.umd.edu. - - - - - - - If the installer asks for web site name and CentOS directory separately, you might - enter: - - - Web site name: mirror.umd.edu - - - CentOS directory: centos/6/os/x86_64 - - - 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. - - - Storage devices - If prompted about which type of devices your installation uses, choose Basic - Storage Devices. - - - Hostname - The installer may ask you to choose a host name. The default - (localhost.localdomain) is fine. You install the cloud-init package later, which sets the host name on - boot when a new instance is provisioned using this image. - - - Partition the disks - There are different options for partitioning the disks. The default installation uses - LVM partitions, and creates three partitions (/boot, - /, swap), which works fine. Alternatively, you might want to - create a single ext4 partition that is mounted to "/", which also - works fine. - If unsure, use the default partition scheme for the installer because no scheme is - better than another. - - - Step through the installation - Step through the installation, using the default options. The simplest thing to do is - to choose the "Basic Server" install (may be called "Server" install on older versions - of CentOS), which installs an SSH server. - - - Detach the CD-ROM and reboot - When the installation has completed, the Congratulations, your CentOS installation - is complete screen appears. - - - - - - To eject a disk by using the virsh command, libvirt requires that - you attach an empty disk at the same target that the CDROM was previously attached, - which should be hdc. You can confirm the appropriate target using the - virsh dumpxml vm-image command. - # virsh dumpxml centos-6.4 -<domain type='kvm'> - <name>centos-6.4</name> -... - <disk type='block' device='cdrom'> - <driver name='qemu' type='raw'/> - <target dev='hdc' bus='ide'/> - <readonly/> - <address type='drive' controller='0' bus='1' target='0' unit='0'/> - </disk> -... -</domain> - - 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. - # virsh attach-disk --type cdrom --mode readonly centos-6.4 "" hdc -# virsh destroy centos-6.4 -# virsh start centos-6.4 - - - Log in to newly created image - When you boot for the first time after installation, you might be prompted about - authentication tools. Select Exit. Then, log in as root. - - - Install the ACPI service - To enable the hypervisor to reboot or shutdown an instance, you - must install and run the acpid service on the guest - system. - Run the following commands inside the CentOS guest to install the - ACPI service and configure it to start when the system - boots: - # yum install acpid -# chkconfig acpid on - - - Configure to fetch metadata - An instance must interact with the metadata service to perform several tasks on start - up. For example, the instance must get the ssh public key and run the user data script. - To ensure that the instance performs these tasks, use one of these methods: - - - Install a cloud-init RPM, which is a - port of the Ubuntu cloud-init package. This is the recommended approach. - - - Modify /etc/rc.local to fetch desired information from - the metadata service, as described in the next section. - - - - - Use cloud-init to fetch the public key - The cloud-init package automatically fetches - the public key from the metadata server and places the key in an account. You can - install cloud-init inside the CentOS guest by - adding the EPEL repo: - # yum install http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm -# yum install cloud-init - 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. - You can change the name of the account used by cloud-init by editing the /etc/cloud/cloud.cfg - file and adding a line with a different user. For example, to configure cloud-init to put the key in an account named - admin, add this line to the configuration file: - user: admin - - - Write a script to fetch the public key (if no cloud-init) - If you are not able to install the cloud-init - package in your image, to fetch the ssh public key and add it to the root account, edit - the /etc/rc.d/rc.local file and add the following lines before the line - touch /var/lock/subsys/local: - if [ ! -d /root/.ssh ]; then - mkdir -p /root/.ssh - chmod 700 /root/.ssh -fi - -# Fetch public key using HTTP -ATTEMPTS=30 -FAILED=0 -while [ ! -f /root/.ssh/authorized_keys ]; do - curl -f http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key \ - > /tmp/metadata-key 2>/dev/null - if [ \$? -eq 0 ]; then - cat /tmp/metadata-key >> /root/.ssh/authorized_keys - chmod 0600 /root/.ssh/authorized_keys - restorecon /root/.ssh/authorized_keys - rm -f /tmp/metadata-key - echo "Successfully retrieved public key from instance metadata" - echo "*****************" - echo "AUTHORIZED KEYS" - echo "*****************" - cat /root/.ssh/authorized_keys - echo "*****************" - fi -done - - Some VNC clients replace the colon (:) with a semicolon - (;) and the underscore (_) with a hyphen - (-). Make sure to specify http: and not - http;. Make sure to specify - authorized_keys and not - authorized-keys. - - - The previous script only gets the ssh public key from the metadata server. It does - not get user data, which is optional data that can be passed by the user when - requesting a new instance. User data is often used to run a custom script when an - instance boots. - As the OpenStack metadata service is compatible with version 2009-04-04 of the - Amazon EC2 metadata service, consult the Amazon EC2 documentation on Using Instance Metadata for details on how to get user data. - - - - Disable the zeroconf route - For the instance to access the metadata service, you must disable the default zeroconf - route: - # echo "NOZEROCONF=yes" >> /etc/sysconfig/network - - - Configure console - For the nova console-log command to work properly on CentOS - 6.x, you might need to add the following lines to the - /boot/grub/menu.lst file: - serial --unit=0 --speed=115200 -terminal --timeout=10 console serial -# Edit the kernel line to add the console entries -kernel ... console=tty0 console=ttyS0,115200n8 - - - Shut down the instance - From inside the instance, as root: - # /sbin/shutdown -h now - - - Clean up (remove MAC address details) - 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. - There is a utility called virt-sysprep, that performs various - cleanup tasks such as removing the MAC address references. It will clean up a virtual - machine image in place: - # virt-sysprep -d centos-6.4 - - - Undefine the libvirt domain - Now that you can upload the image to the Image service, you no longer need to have - this virtual machine image managed by libvirt. Use the virsh undefine - vm-image command to inform libvirt: - # virsh undefine centos-6.4 - - - Image is complete - The underlying image file that you created with qemu-img create is - ready to be uploaded. For example, you can upload the - /tmp/centos-6.4.qcow2 image to the Image service. - -
diff --git a/doc/image-guide/section_fedora-example.xml b/doc/image-guide/section_fedora-example.xml deleted file mode 100644 index fc69c15f32..0000000000 --- a/doc/image-guide/section_fedora-example.xml +++ /dev/null @@ -1,169 +0,0 @@ - - -%openstack; -]> -
- Example: Fedora image - Download a Fedora - ISO image. This procedure lets you create a Fedora 20 image. - - Start the installation using virt-install as shown below: -# qemu-img create -f qcow2 fedora-20.qcow2 8G -# virt-install --connect=qemu:///system --network=bridge:virbr0 \ ---extra-args="console=tty0 console=ttyS0,115200 serial rd_NO_PLYMOUTH" \ ---name=fedora-20 --disk path=/var/lib/libvirt/images/fedora-20.qcow2,format=qcow2,size=10,cache=none \ ---ram 2048 --vcpus=2 --check-cpu --accelerate --os-type linux --os-variant fedora19 \ ---hvm --location=http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/ \ ---nographics - This will launch a VM and start the installation process. -Starting install... -Retrieving file .treeinfo... | 2.2 kB 00:00:00 !!! -Retrieving file vmlinuz... | 9.8 MB 00:00:05 !!! -Retrieving file initrd.img... | 66 MB 00:00:37 !!! -Allocating 'fedora-20.qcow2' | 10 GB 00:00:00 -Creating domain... | 0 B 00:00:00 -Connected to domain fedora-20 -Escape character is ^] -[ 0.000000] Initializing cgroup subsys cpuset -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Initializing cgroup subsys cpuacct -... -... -... -[ OK ] Reached target Local File Systems (Pre). -Starting installer, one moment... -anaconda 20.25.15-1 for Fedora 20 started. -================================================================================ -=============================================================================== - - Choose the VNC or text mode to set the installation options. -Text mode provides a limited set of installation -options. It does not offer custom partitioning for full control over the -disk layout. Would you like to use VNC mode instead? - -1) Start VNC - -2) Use text mode - -Please make your choice from above ['q' to quit | 'c' to continue | -'r' to refresh]: - Set the timezone, network configuration, installation - source, and the root password. Optionally, - you can choose to create a user. - Set up the installation destination as shown below: -================================================================================ -Probing storage... -Installation Destination - -[x] 1) Virtio Block Device: 10.24 GB (vda) - -1 disk selected; 10.24 GB capacity; 10.24 GB free ... - -Please make your choice from above ['q' to quit | 'c' to continue | -'r' to refresh]: c -================================================================================ -================================================================================ -Autopartitioning Options - -[ ] 1) Replace Existing Linux system(s) - -[x] 2) Use All Space - -[ ] 3) Use Free Space - -Installation requires partitioning of your hard drive. Select what space to use -for the install target. - -Please make your choice from above ['q' to quit | 'c' to continue | -'r' to refresh]: 2 -================================================================================ -================================================================================ -Autopartitioning Options - -[ ] 1) Replace Existing Linux system(s) - -[x] 2) Use All Space - -[ ] 3) Use Free Space - -Installation requires partitioning of your hard drive. Select what space to use -for the install target. - -Please make your choice from above ['q' to quit | 'c' to continue | -'r' to refresh]: c -================================================================================ -================================================================================ -Partition Scheme Options - -[ ] 1) Standard Partition - -[x] 2) LVM - -[ ] 3) BTRFS - -Select a partition scheme configuration. - -Please make your choice from above ['q' to quit | 'c' to continue | -'r' to refresh]: c -Generating updated storage configuration -Checking storage configuration... -================================================================================ -Run the following commands from the host to eject the disk and - reboot using virsh, as root. -# virsh attach-disk --type cdrom --mode readonly fedora-20 "" hdc -# virsh destroy fedora-20 -# virsh start fedora-20 - You can also use the GUI to detach and reboot it by manually - stopping and starting. - Log in as root user when you boot for the first time after - installation. - Install and run the acpid service on the guest - system to enable the virtual machine to reboot or shutdown an instance. - Run the following commands inside the Fedora guest to install the - ACPI service and configure it to start when the system boots: -# yum install acpid -# chkconfig acpid on -Install cloud-init package inside the Fedora - guest by adding the EPEL repo: - The cloud-init package automatically fetches - the public key from the metadata server and places the key in an account. -# yum install http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm -# yum install cloud-init - You can change the name of the account used by cloud-init - by editing the /etc/cloud/cloud.cfg file and - adding a line with a different user. For example, to configure - cloud-init to put the key in an account named - admin, add this line to the configuration file: -user: admin -Disable the default zeroconf route for the - instance to access the metadata service: -# echo "NOZEROCONF=yes" >> /etc/sysconfig/network - For the nova console-log command to work - properly on Fedora 20, you might need to add the following lines to - the /boot/grub/menu.lst file: -serial --unit=0 --speed=115200 -terminal --timeout=10 console serial -# Edit the kernel line to add the console entries -kernel ... console=tty0 console=ttyS0,115200n8 - Shut down the instance from inside the instance as a root user: -# /sbin/shutdown -h now - Clean up and remove MAC address details. - 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. - Use the virt-sysprep utility. This performs - various cleanup tasks such as removing the MAC address references. - It will clean up a virtual machine image in place: -# virt-sysprep -d fedora-20 - Undefine the domain since you no longer need to have this - virtual machine image managed by libvirt: -# virsh undefine fedora-20 - -The underlying image file that you created with qemu-img create is - ready to be uploaded to the Image service. -
diff --git a/doc/image-guide/section_freebsd-example.xml b/doc/image-guide/section_freebsd-example.xml deleted file mode 100644 index 77e552635f..0000000000 --- a/doc/image-guide/section_freebsd-example.xml +++ /dev/null @@ -1,268 +0,0 @@ - - -%openstack; -]> -
- Example: FreeBSD image - This example creates a minimal FreeBSD image that is - compatible with OpenStack and - bsd-cloudinit. The - bsd-cloudinit program is - independently maintained and in active development. The best - source of information on the current state of the project is at - http://pellaeon.github.io/bsd-cloudinit/. - KVM with virtio drivers is used as the virtualization platform - because that is the most widely used among OpenStack operators. If - you use a different platform for your cloud virtualization, use - that same platform in the image creation step. - This example shows how to create a FreeBSD 10 image. To create - a FreeBSD 9.2 image, follow these steps with the noted - differences. - - To create a FreeBSD image - - Make a virtual drive: - $ qemu-img create -f qcow2 freebsd.qcow2 1G - The minimum supported disk size for FreeBSD is 1 GB. - Because the goal is to make the smallest possible base image, - the example uses that minimum size. This size is sufficient to - include the optional doc, - games, and lib32 - collections. To include the ports - collection, add another 1 GB. To include - src, add 512 MB. - - - Get the installer ISO: - $ curl ftp://ftp.freebsd.org/pub/FreeBSD/releases\ -/amd64/amd64/ISO-IMAGES/10.1/FreeBSD-10.1-RELEASE-amd64-bootonly.iso >\ -FreeBSD-10.1-RELEASE-amd64-bootonly.iso - - - Launch a VM on your local workstation. Use the same - hypervisor, virtual disk, and virtual network drivers as you - use in your production environment. - The following command uses the minimum amount of RAM, - which is 256 MB: - $ kvm -smp 1 -m 256 -cdrom FreeBSD-10.1-RELEASE-amd64-bootonly.iso \ --drive if=virtio,file=freebsd.qcow2 \ --net nic,model=virtio -net user - You can specify up to 1 GB additional RAM to make the - installation process run faster. - This VM must also have Internet access to download - packages. - - By using the same hypervisor, you can ensure that you - emulate the same devices that exist in production. However, - if you use full hardware virtualization instead of - paravirtualization, you do not need to use the same - hypervisor; you must use the same type of virtualized - hardware because FreeBSD device names are related to their - drivers. If the name of your root block device or primary - network interface in production differs than the names used - during image creation, errors can occur. - - You now have a VM that boots from the downloaded install - ISO and is connected to the blank virtual disk that you - created previously. - - - To install the operating system, complete the following - steps inside the VM: - - - When prompted, choose to run the ISO in - Install mode. - - - Accept the default keymap or select an appropriate - mapping for your needs. - - - Provide a host name for your image. If you use - bsd-cloudinit, it overrides - this value with the name provided by OpenStack when an - instance boots from this image. - - - When prompted about the optional - doc, games, - lib32, ports, and - src system components, select only - those that you need. It is possible to have a fully - functional installation without selecting additional - components selected. As noted previously, a minimal system - with a 1 GB virtual disk supports - doc, games, and - lib32 inclusive. The - ports collection requires at least - 1 GB additional space and possibly more if you plan - to install many ports. The src - collection requires an additional 512 MB. - - - Configure the primary network interface to use DHCP. - In this example, which uses a virtio network device, this - interface is named vtnet0. - - - Accept the default network mirror. - - - Set up disk partitioning. - Disk partitioning is a critical element of the image - creation process and the auto-generated default - partitioning scheme does not work with - bsd-cloudinit at this - time. - Because the default does not work, you must select - manual partitioning. The partition editor should list only - one block device. If you use virtio for the disk device - driver, it is named vtbd0. Select this - device and run the create command three - times: - - - Select Create to create a - partition table. This action is the default when no - partition table exists. Then, select GPT - GUID Partition Table from the list. This - choice is the default. - - - Create two partitions: - - First partition: A 64 kB - freebsd-boot partition with - no mount point. - - - Second partition: A - freebsd-ufs partition with - a mount point of / with all - remaining free space. - - - - - The following figure shows a completed partition table - with a 1 GB virtual disk: - - - - - - Select Finish and then - Commit to commit your - changes. - - If you modify this example, the root partition, - which is mounted on /, must be the - last partition on the drive so that it can expand at run - time to the disk size that your instance type provides. - Also note that bsd-cloudinit - currently has a hard-coded assumption that this is the - second partition. - - - - - - Select a root password. - - - Select the CMOS time zone. - The virtualized CMOS almost always stores its time in UTC, - so unless you know otherwise, select UTC. - - - Select the time zone appropriate to your - environment. - - - From the list of services to start on boot, you must - select ssh. - Optionally, select other services. - - - Optionally, add users. - You do not need to add users at this time. The - bsd-cloudinit program adds a - freebsd user account if one does not - exist. The ssh keys - for this user are associated with OpenStack. To customize this - user account, you can create it now. For example, you might - want to customize the shell for the user. - - - Final config - This menu enables you to update previous settings. Check - that the settings are correct, and click - exit. - - - After you exit, you can open a shell to complete manual - configuration steps. Select Yes to make - a few OpenStack-specific changes: - - - Set up the console: - # echo 'console="comconsole,vidconsole"' >> /boot/loader.conf - This sets console output to go to the serial console, - which is displayed by nova consolelog, - and the video console for sites with VNC or Spice - configured. - - - Minimize boot delay: - # echo 'autoboot_delay="1"' >> /boot/loader.conf - - - Download the latest - bsd-cloudinit-installer. The - download commands differ between FreeBSD 10.1 and 9.2 - because of differences in how the fetch - command handles HTTPS URLs. - In FreeBSD 10.1 the fetch command - verifies SSL peers by default, so you need to install the - ca_root_nss package that contains - certificate authority root certificates and tell - fetch where to find them. For FreeBSD - 10.1 run these commands: - # pkg install ca_root_nss -# fetch --ca-cert=/usr/local/share/certs/ca-root-nss.crt \ -https://raw.github.com/pellaeon/bsd-cloudinit-installer/master/installer.sh - FreeBSD 9.2 fetch does not support - peer-verification for https. For FreeBSD 9.2, run this - command: - # fetch https://raw.github.com/pellaeon/bsd-cloudinit-installer/master/installer.sh - - - Run the installer: - # sh ./installer.sh - Issue this command to download and install the latest - bsd-cloudinit package, and install the - necessary prerequisites. - - - Install sudo and configure the - freebsd user to have passwordless - access: - # pkg install sudo -# echo 'freebsd ALL=(ALL) NOPASSWD: ALL' > /usr/local/etc/sudoers.d/10-cloudinit - - - - - Power off the system: - # shutdown -h now - - -
diff --git a/doc/image-guide/section_glance-image-metadata.xml b/doc/image-guide/section_glance-image-metadata.xml deleted file mode 100644 index 488978fffc..0000000000 --- a/doc/image-guide/section_glance-image-metadata.xml +++ /dev/null @@ -1,80 +0,0 @@ - -
- Image metadata - - Image metadata can help end users determine the nature of an image, and is used by - associated OpenStack components and drivers which interface with the Image service. - Metadata can also determine the scheduling of hosts. If the option - is set on an image, and Compute is configured so that the - ImagePropertiesFilter scheduler filter is enabled (default), then the - scheduler only considers compute hosts that satisfy that property. - Compute's ImagePropertiesFilter value is specified in the - value in the - /etc/nova/nova.conf file. - You can add metadata to Image service images by using the --property - key=value parameter with the - glance image-create or glance image-update command. More - than one property can be specified. For example: - $ glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu - Common image properties are also specified in the - /etc/glance/schema-image.json file. For a complete list of valid property - keys and values, refer to the OpenStack - Command-Line Reference. - All associated properties for an image can be displayed using the glance - image-show command. For example: - $ glance image-show myCirrosImage -+---------------------------------------+--------------------------------------+ -| Property | Value | -+---------------------------------------+--------------------------------------+ -| Property 'base_image_ref' | 397e713c-b95b-4186-ad46-6126863ea0a9 | -| Property 'image_location' | snapshot | -| Property 'image_state' | available | -| Property 'image_type' | snapshot | -| Property 'instance_type_ephemeral_gb' | 0 | -| Property 'instance_type_flavorid' | 2 | -| Property 'instance_type_id' | 5 | -| Property 'instance_type_memory_mb' | 2048 | -| Property 'instance_type_name' | m1.small | -| Property 'instance_type_root_gb' | 20 | -| Property 'instance_type_rxtx_factor' | 1 | -| Property 'instance_type_swap' | 0 | -| Property 'instance_type_vcpu_weight' | None | -| Property 'instance_type_vcpus' | 1 | -| Property 'instance_uuid' | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | -| Property 'kernel_id' | df430cc2-3406-4061-b635-a51c16e488ac | -| Property 'owner_id' | 66265572db174a7aa66eba661f58eb9e | -| Property 'ramdisk_id' | 3cf852bd-2332-48f4-9ae4-7d926d50945e | -| Property 'user_id' | 376744b5910b4b4da7d8e6cb483b06a8 | -| checksum | 8e4838effa1969ad591655d6485c7ba8 | -| container_format | ami | -| created_at | 2013-07-22T19:45:58 | -| deleted | False | -| disk_format | ami | -| id | 7e5142af-1253-4634-bcc6-89482c5f2e8a | -| is_public | False | -| min_disk | 0 | -| min_ram | 0 | -| name | myCirrosImage | -| owner | 66265572db174a7aa66eba661f58eb9e | -| protected | False | -| size | 14221312 | -| status | active | -| updated_at | 2013-07-22T19:46:42 | -+---------------------------------------+--------------------------------------+ - - - Volume-from-Image properties - When creating Block Storage volumes from images, also consider your - configured image properties. If you alter the core image properties, you - should also update your Block Storage configuration. Amend - in the - /etc/cinder/cinder.conf file on all controller - nodes to match the core properties you have set in the Image - service. - -
diff --git a/doc/image-guide/section_glance_image-formats.xml b/doc/image-guide/section_glance_image-formats.xml deleted file mode 100644 index 57408aabc4..0000000000 --- a/doc/image-guide/section_glance_image-formats.xml +++ /dev/null @@ -1,102 +0,0 @@ - -
- Disk and container formats for images - - When you add an image to the Image service, you can specify - its disk and container formats. -
- Disk formats - 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. - Set the disk format for your image to one of the - following values: - - - raw: An unstructured disk - image format; if you have a file without an - extension it is possibly a raw format. - - - vhd: The VHD disk format, a - common disk format used by virtual machine - monitors from VMware, Xen, Microsoft, VirtualBox, - and others. - - - vmdk: Common disk format - supported by many common virtual machine - monitors. - - - vdi: Supported by VirtualBox - virtual machine monitor and the QEMU - emulator. - - - iso: An archive format for - the data contents of an optical disc, such as - CD-ROM. - - - qcow2: Supported by the QEMU - emulator that can expand dynamically and supports - Copy on Write. - - - aki: An Amazon kernel - image. - - - ari: An Amazon ramdisk - image. - - - ami: An Amazon machine - image. - - -
-
- Container formats - The container format indicates whether the virtual - machine image is in a file format that also contains - metadata about the actual virtual machine. - - 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. - - You can set the container format for your image to one - of the following values: - - - bare. The image does not have - a container or metadata envelope. - - - ovf. The OVF container - format. - - - aki. An Amazon kernel image. - - - - ari. An Amazon ramdisk - image. - - - ami. An Amazon machine - image. - - -
- -
diff --git a/doc/image-guide/section_ubuntu-example.xml b/doc/image-guide/section_ubuntu-example.xml deleted file mode 100644 index 8a4faf2878..0000000000 --- a/doc/image-guide/section_ubuntu-example.xml +++ /dev/null @@ -1,208 +0,0 @@ - -
- Example: Ubuntu image - This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image for a - different version of Ubuntu, follow these steps with the noted differences. - - Download an Ubuntu install ISO - Because the goal is to make the smallest possible base image, this example uses the - network installation ISO. The Ubuntu 64-bit 14.04 network installer ISO is at http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini.iso. - - - Start the install process - Start the installation process by using either virt-manager or - virt-install as described in the previous section. If you use - virt-install, do not forget to connect your VNC client to the - virtual machine. - Assume that the name of your virtual machine image is ubuntu-14.04, - which you need to know when you use virsh commands to manipulate the - state of the image. - If you are using virt-manager, the commands should look something - like this: - # qemu-img create -f qcow2 /tmp/trusty.qcow2 10G -# virt-install --virt-type kvm --name trusty --ram 1024 \ - --cdrom=/data/isos/trusty-64-mini.iso \ - --disk /tmp/trusty.qcow2,format=qcow2 \ - --network network=default \ - --graphics vnc,listen=0.0.0.0 --noautoconsole \ - --os-type=linux --os-variant=ubuntutrusty - - - Step through the install - At the initial Installer boot menu, choose the Install option. - Step through the install prompts, the defaults should be fine. - - - - - - - - Hostname - 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. - - - - Select a mirror - The default mirror proposed by the installer should be fine. - - - Step through the install - Step through the install, using the default options. When prompted for a user name, - the default (ubuntu) is fine. - - - Partition the disks - 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. - If unsure, we recommend you use the installer's default partition scheme, since there - is no clear advantage to one scheme or another. - - - Automatic updates - 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". - - - Software selection: OpenSSH server - Choose "OpenSSH server" so that you will be able to SSH into the virtual machine when - it launches inside of an OpenStack cloud. - - - - - - - - Install GRUB boot loader - Select "Yes" when asked about installing the GRUB boot loader to the master boot - record. - - - - - - For more information on configuring Grub, see - . - - - Detach the CD-ROM and reboot - Select the defaults for all of the remaining options. When the installation is - complete, you will be prompted to remove the CD-ROM. - - - - - - - - There is a known bug in Ubuntu 14.04; when you select - "Continue", the virtual machine will shut down, even though - it says it will reboot. - - To eject a disk using virsh, libvirt requires that you attach an - empty disk at the same target that the CDROM was previously attached, which should be - hdc. You can confirm the appropriate target using the - virsh dumpxml vm-image command. - # virsh dumpxml trusty -<domain type='kvm'> - <name>trusty</name> -... - <disk type='block' device='cdrom'> - <driver name='qemu' type='raw'/> - <target dev='hdc' bus='ide'/> - <readonly/> - <address type='drive' controller='0' bus='1' target='0' unit='0'/> - </disk> -... -</domain> - - 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. - # virsh start trusty --paused -# virsh attach-disk --type cdrom --mode readonly trusty "" hdc -# virsh resume trusty - - In the previous example, you paused the instance, ejected the disk, and - unpaused the instance. In theory, you could have ejected the disk at the - Installation complete screen. However, our testing - indicates that the Ubuntu installer locks the drive so that it cannot be ejected at - that point. - - - - Log in to newly created image - 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. - - - Install cloud-init - The cloud-init script starts on instance boot and will search for a - metadata provider to fetch a public key from. The public key will be placed in the - default user account for the image. - Install the cloud-init package: - # apt-get install cloud-init - When building Ubuntu images cloud-init must be explicitly - configured for the metadata source in use. The OpenStack metadata server emulates the - EC2 metadata service used by images in Amazon EC2. - To set the metadata source to be used by the image run the - dpkg-reconfigure command against the - cloud-init package. When prompted select the - EC2 data source: - # dpkg-reconfigure cloud-init - 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". - 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: - user: admin - - - Shut down the instance - From inside the instance, as root: - # /sbin/shutdown -h now - - - Clean up (remove MAC address details) - The operating system records the MAC address of the virtual Ethernet card in locations - such as /etc/udev/rules.d/70-persistent-net.rules during the - installation process. However, each time the image boots up, the virtual Ethernet card will - have a different MAC address, so this information must be deleted from the configuration - file. - There is a utility called virt-sysprep, that performs various - cleanup tasks such as removing the MAC address references. It will clean up a virtual - machine image in place: - # virt-sysprep -d trusty - - - Undefine the libvirt domain - 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 virsh undefine - vm-image command to inform libvirt: - # virsh undefine trusty - - - Image is complete - The underlying image file that you created with qemu-img create, - such as /tmp/trusty.qcow2, is now ready for uploading to the - OpenStack Image service. - -
diff --git a/doc/image-guide/section_windows-example.xml b/doc/image-guide/section_windows-example.xml deleted file mode 100644 index c31f450cca..0000000000 --- a/doc/image-guide/section_windows-example.xml +++ /dev/null @@ -1,105 +0,0 @@ - - -%openstack; -]> -
- Example: Microsoft Windows image - This example creates a Windows Server 2012 qcow2 image, using - virt-install and the KVM hypervisor. - - - - Follow these steps to prepare the installation: - - - Download a Windows Server 2012 installation ISO. Evaluation - images are available on the - Microsoft website (registration required). - - - Download the signed VirtIO drivers ISO from the Fedora - website. - - - Create a 15 GB qcow2 image: - $ qemu-img create -f qcow2 ws2012.qcow2 15G - - - - - Start the Windows Server 2012 installation with the - virt-install command: - # virt-install --connect qemu:///system \ - --name ws2012 --ram 2048 --vcpus 2 \ - --network network=default,model=virtio \ - --disk path=ws2012.qcow2,format=qcow2,device=disk,bus=virtio \ - --cdrom /path/to/en_windows_server_2012_x64_dvd.iso \ - --disk path=/path/to/virtio-win-0.1-XX.iso,device=cdrom \ - --vnc --os-type windows --os-variant win2k8 - Use virt-manager or - virt-viewer to connect to the VM and start the - Windows installation. - - - Enable the VirtIO drivers. - The disk is not detected by default by the Windows installer. When - requested to choose an installation target, click Load - driver and browse the file system to select the - E:\WIN8\AMD64 folder. The Windows installer - displays a list of drivers to install. Select the VirtIO SCSI and - network drivers, and continue the installation. - Once the installation is completed, the VM restarts. Define a - password for the administrator when prompted. - - - Log in as administrator and start a command window. - - - Complete the VirtIO drivers installation by running the - following command: - C:\pnputil -i -a E:\WIN8\AMD64\*.INF - - - To allow Cloudbase-Init to run scripts - during an instance boot, set the PowerShell execution policy to be - unrestricted: - C:\powershell -C:\Set-ExecutionPolicy Unrestricted - - - Download and install Cloudbase-Init: - C:\Invoke-WebRequest -UseBasicParsing http://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x64.msi -OutFile cloudbaseinit.msi -C:\.\cloudbaseinit.msi - In the configuration options window, change the following settings: - - - Username: Administrator - - - Network adapter to configure: - Red Hat VirtIO Ethernet Adapter - - - Serial port for logging: COM1 - - - When the installation is done, in the Complete the - Cloudbase-Init Setup Wizard window, select the - Run Sysprep and Shutdown - check boxes and click Finish. - Wait for the machine shutdown. - - - - Your image is ready to upload to the Image service: - $ glance image-create --name WS2012 --disk-format qcow2 \ - --container-format bare --is-public true \ - --file ws2012.qcow2 -
diff --git a/doc/image-guide-rst/setup.cfg b/doc/image-guide/setup.cfg similarity index 100% rename from doc/image-guide-rst/setup.cfg rename to doc/image-guide/setup.cfg diff --git a/doc/image-guide-rst/setup.py b/doc/image-guide/setup.py similarity index 100% rename from doc/image-guide-rst/setup.py rename to doc/image-guide/setup.py diff --git a/doc/image-guide-rst/source/centos-image.rst b/doc/image-guide/source/centos-image.rst similarity index 100% rename from doc/image-guide-rst/source/centos-image.rst rename to doc/image-guide/source/centos-image.rst diff --git a/doc/image-guide-rst/source/common b/doc/image-guide/source/common similarity index 100% rename from doc/image-guide-rst/source/common rename to doc/image-guide/source/common diff --git a/doc/image-guide-rst/source/conf.py b/doc/image-guide/source/conf.py similarity index 100% rename from doc/image-guide-rst/source/conf.py rename to doc/image-guide/source/conf.py diff --git a/doc/image-guide-rst/source/convert-images.rst b/doc/image-guide/source/convert-images.rst similarity index 100% rename from doc/image-guide-rst/source/convert-images.rst rename to doc/image-guide/source/convert-images.rst diff --git a/doc/image-guide-rst/source/create-images-automatically.rst b/doc/image-guide/source/create-images-automatically.rst similarity index 100% rename from doc/image-guide-rst/source/create-images-automatically.rst rename to doc/image-guide/source/create-images-automatically.rst diff --git a/doc/image-guide-rst/source/create-images-manually.rst b/doc/image-guide/source/create-images-manually.rst similarity index 100% rename from doc/image-guide-rst/source/create-images-manually.rst rename to doc/image-guide/source/create-images-manually.rst diff --git a/doc/image-guide-rst/source/fedora-image.rst b/doc/image-guide/source/fedora-image.rst similarity index 100% rename from doc/image-guide-rst/source/fedora-image.rst rename to doc/image-guide/source/fedora-image.rst diff --git a/doc/image-guide-rst/source/figures/centos-complete.png b/doc/image-guide/source/figures/centos-complete.png similarity index 100% rename from doc/image-guide-rst/source/figures/centos-complete.png rename to doc/image-guide/source/figures/centos-complete.png diff --git a/doc/image-guide-rst/source/figures/centos-install-method.png b/doc/image-guide/source/figures/centos-install-method.png similarity index 100% rename from doc/image-guide-rst/source/figures/centos-install-method.png rename to doc/image-guide/source/figures/centos-install-method.png diff --git a/doc/image-guide-rst/source/figures/centos-install.png b/doc/image-guide/source/figures/centos-install.png similarity index 100% rename from doc/image-guide-rst/source/figures/centos-install.png rename to doc/image-guide/source/figures/centos-install.png diff --git a/doc/image-guide-rst/source/figures/centos-tcpip.png b/doc/image-guide/source/figures/centos-tcpip.png similarity index 100% rename from doc/image-guide-rst/source/figures/centos-tcpip.png rename to doc/image-guide/source/figures/centos-tcpip.png diff --git a/doc/image-guide-rst/source/figures/centos-url-setup.png b/doc/image-guide/source/figures/centos-url-setup.png similarity index 100% rename from doc/image-guide-rst/source/figures/centos-url-setup.png rename to doc/image-guide/source/figures/centos-url-setup.png diff --git a/doc/image-guide-rst/source/figures/freebsd-partitions.png b/doc/image-guide/source/figures/freebsd-partitions.png similarity index 100% rename from doc/image-guide-rst/source/figures/freebsd-partitions.png rename to doc/image-guide/source/figures/freebsd-partitions.png diff --git a/doc/image-guide-rst/source/figures/ubuntu-finished.png b/doc/image-guide/source/figures/ubuntu-finished.png similarity index 100% rename from doc/image-guide-rst/source/figures/ubuntu-finished.png rename to doc/image-guide/source/figures/ubuntu-finished.png diff --git a/doc/image-guide-rst/source/figures/ubuntu-grub.png b/doc/image-guide/source/figures/ubuntu-grub.png similarity index 100% rename from doc/image-guide-rst/source/figures/ubuntu-grub.png rename to doc/image-guide/source/figures/ubuntu-grub.png diff --git a/doc/image-guide-rst/source/figures/ubuntu-install.png b/doc/image-guide/source/figures/ubuntu-install.png similarity index 100% rename from doc/image-guide-rst/source/figures/ubuntu-install.png rename to doc/image-guide/source/figures/ubuntu-install.png diff --git a/doc/image-guide-rst/source/figures/ubuntu-software-selection.png b/doc/image-guide/source/figures/ubuntu-software-selection.png similarity index 100% rename from doc/image-guide-rst/source/figures/ubuntu-software-selection.png rename to doc/image-guide/source/figures/ubuntu-software-selection.png diff --git a/doc/image-guide-rst/source/figures/virt-manager.png b/doc/image-guide/source/figures/virt-manager.png similarity index 100% rename from doc/image-guide-rst/source/figures/virt-manager.png rename to doc/image-guide/source/figures/virt-manager.png diff --git a/doc/image-guide-rst/source/freebsd-image.rst b/doc/image-guide/source/freebsd-image.rst similarity index 100% rename from doc/image-guide-rst/source/freebsd-image.rst rename to doc/image-guide/source/freebsd-image.rst diff --git a/doc/image-guide-rst/source/image-formats.rst b/doc/image-guide/source/image-formats.rst similarity index 100% rename from doc/image-guide-rst/source/image-formats.rst rename to doc/image-guide/source/image-formats.rst diff --git a/doc/image-guide-rst/source/image-metadata.rst b/doc/image-guide/source/image-metadata.rst similarity index 100% rename from doc/image-guide-rst/source/image-metadata.rst rename to doc/image-guide/source/image-metadata.rst diff --git a/doc/image-guide-rst/source/index.rst b/doc/image-guide/source/index.rst similarity index 92% rename from doc/image-guide-rst/source/index.rst rename to doc/image-guide/source/index.rst index 751bcd0357..4987b70012 100644 --- a/doc/image-guide-rst/source/index.rst +++ b/doc/image-guide/source/index.rst @@ -8,8 +8,6 @@ Abstract This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack. -.. warning:: This guide is a work-in-progress. - Contents ~~~~~~~~ diff --git a/doc/image-guide-rst/source/introduction.rst b/doc/image-guide/source/introduction.rst similarity index 100% rename from doc/image-guide-rst/source/introduction.rst rename to doc/image-guide/source/introduction.rst diff --git a/doc/image-guide/source/locale/image-guide.pot b/doc/image-guide/source/locale/image-guide.pot new file mode 100644 index 0000000000..e69de29bb2 diff --git a/doc/image-guide-rst/source/modify-images.rst b/doc/image-guide/source/modify-images.rst similarity index 100% rename from doc/image-guide-rst/source/modify-images.rst rename to doc/image-guide/source/modify-images.rst diff --git a/doc/image-guide-rst/source/net-running.rst b/doc/image-guide/source/net-running.rst similarity index 100% rename from doc/image-guide-rst/source/net-running.rst rename to doc/image-guide/source/net-running.rst diff --git a/doc/image-guide-rst/source/obtain-images.rst b/doc/image-guide/source/obtain-images.rst similarity index 100% rename from doc/image-guide-rst/source/obtain-images.rst rename to doc/image-guide/source/obtain-images.rst diff --git a/doc/image-guide-rst/source/openstack-images.rst b/doc/image-guide/source/openstack-images.rst similarity index 100% rename from doc/image-guide-rst/source/openstack-images.rst rename to doc/image-guide/source/openstack-images.rst diff --git a/doc/image-guide-rst/source/ubuntu-image.rst b/doc/image-guide/source/ubuntu-image.rst similarity index 100% rename from doc/image-guide-rst/source/ubuntu-image.rst rename to doc/image-guide/source/ubuntu-image.rst diff --git a/doc/image-guide-rst/source/virt-install.rst b/doc/image-guide/source/virt-install.rst similarity index 100% rename from doc/image-guide-rst/source/virt-install.rst rename to doc/image-guide/source/virt-install.rst diff --git a/doc/image-guide-rst/source/virt-manager.rst b/doc/image-guide/source/virt-manager.rst similarity index 100% rename from doc/image-guide-rst/source/virt-manager.rst rename to doc/image-guide/source/virt-manager.rst diff --git a/doc/image-guide-rst/source/windows-image.rst b/doc/image-guide/source/windows-image.rst similarity index 100% rename from doc/image-guide-rst/source/windows-image.rst rename to doc/image-guide/source/windows-image.rst diff --git a/doc/pom.xml b/doc/pom.xml index d2a3ce3f45..1aed472933 100644 --- a/doc/pom.xml +++ b/doc/pom.xml @@ -14,7 +14,6 @@ cli-reference config-reference glossary - image-guide diff --git a/tools/build-all-rst.sh b/tools/build-all-rst.sh index 5437caa75f..dfef875329 100755 --- a/tools/build-all-rst.sh +++ b/tools/build-all-rst.sh @@ -11,7 +11,8 @@ if [[ $# > 0 ]] ; then fi fi -for guide in user-guide user-guide-admin networking-guide admin-guide-cloud contributor-guide; do +for guide in user-guide user-guide-admin networking-guide admin-guide-cloud \ + contributor-guide image-guide; do tools/build-rst.sh doc/$guide $GLOSSARY --build build \ --target $guide $LINKCHECK # Build it only the first time @@ -19,7 +20,7 @@ for guide in user-guide user-guide-admin networking-guide admin-guide-cloud cont done # Draft guides -for guide in arch-design-rst config-ref-rst image-guide-rst; do +for guide in arch-design-rst config-ref-rst; do tools/build-rst.sh doc/$guide --build build \ --target "draft/$guide" $LINKCHECK done diff --git a/www/static/.htaccess b/www/static/.htaccess index 53df2d094a..0b92212b33 100644 --- a/www/static/.htaccess +++ b/www/static/.htaccess @@ -159,6 +159,7 @@ redirect 301 /admin-guide-cloud/content/customize-flavors.html /admin-guide-clou redirectmatch 301 "^/user-guide/content/.*$" /user-guide/index.html redirectmatch 301 "^/user-guide-admin/content/.*" /user-guide-admin/index.html redirectmatch 301 "^/admin-guide-cloud/content/.*$" /admin-guide-cloud/index.html +redirectmatch 301 "^/image-guide/content/.*$" /image-guide/index.html # Hot-guide has moved to heat repo redirect 301 /user-guide/hot-guide/hot.html /developer/heat/template_guide/hot_guide.html