openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
Change-Id: Iee8109a745638c0520719524613e5cf697c87322
This commit is contained in:
OpenStack Jenkins 2014-03-21 06:26:19 +00:00
parent 3160afa901
commit 1d5442ceb8
12 changed files with 3050 additions and 2822 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1106
doc/admin-guide-cloud/locale/admin-guide-cloud.pot
View File

File diff suppressed because it is too large Load Diff

2
doc/cli-reference/locale/cli-reference.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-03-20 06:22+0000\n"
"POT-Creation-Date: 2014-03-21 06:24+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

848
doc/common/locale/common.pot
View File

File diff suppressed because one or more lines are too long

454
doc/config-reference/locale/config-reference.pot
View File

File diff suppressed because it is too large Load Diff

2444
doc/glossary/locale/glossary.pot
View File

File diff suppressed because it is too large Load Diff

2
doc/high-availability-guide/locale/high-availability-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-03-20 06:23+0000\n"
"POT-Creation-Date: 2014-03-21 06:24+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

174
doc/image-guide/locale/image-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-03-20 06:23+0000\n"
"POT-Creation-Date: 2014-03-21 06:24+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -9,235 +9,235 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ./doc/image-guide/ch_modifying_images.xml:6(title)
#: ./doc/image-guide/ch_modifying_images.xml:10(title)
msgid "Modify images"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:12(para)
#: ./doc/image-guide/ch_modifying_images.xml:16(para)
msgid "Do not attempt to use these tools to modify an image that is attached to a running virtual machine. These tools are designed to only modify images that are not currently running."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:8(para)
#: ./doc/image-guide/ch_modifying_images.xml:12(para)
msgid "Once you have obtained a virtual machine image, you may want to make some changes to it before uploading it to the OpenStack Image service. Here we describe several tools available that allow you to modify images.<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:18(title)
#: ./doc/image-guide/ch_modifying_images.xml:22(title)
msgid "guestfish"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:19(para)
#: ./doc/image-guide/ch_modifying_images.xml:23(para)
msgid "The <placeholder-1/> program is a tool from the <link href=\"http://libguestfs.org/\">libguestfs</link> project that allows you to modify the files inside of a virtual machine image."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:24(para)
#: ./doc/image-guide/ch_modifying_images.xml:28(para)
msgid "<placeholder-1/> does not mount the image directly into the local file system. Instead, it provides you with a shell interface that enables you to view, edit, and delete files. Many of <placeholder-2/> commands, such as <placeholder-3/>, <placeholder-4/>, and <placeholder-5/>, resemble traditional bash commands."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:34(title)
#: ./doc/image-guide/ch_modifying_images.xml:38(title)
msgid "Example guestfish session"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:35(para)
#: ./doc/image-guide/ch_modifying_images.xml:39(para)
msgid "Sometimes, you must modify a virtual machine image to remove any traces of the MAC address that was assigned to the virtual network interface card when the image was first created, because the MAC address will be different when it boots the next time. This example shows how to use guestfish to remove references to the old MAC address by deleting the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file and removing the <literal>HWADDR</literal> line from the <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> file."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:47(para)
#: ./doc/image-guide/ch_modifying_images.xml:51(para)
msgid "Assume that you have a CentOS qcow2 image called <filename>centos63_desktop.img</filename>. Mount the image in read-write mode as root, as follows:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:61(para)
#: ./doc/image-guide/ch_modifying_images.xml:65(para)
msgid "This starts a guestfish session. Note that the guestfish prompt looks like a fish: <literal>&gt; &lt;fs&gt;</literal>."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:64(para)
#: ./doc/image-guide/ch_modifying_images.xml:68(para)
msgid "We must first use the <placeholder-1/> command at the guestfish prompt before we can do anything else. This will launch a virtual machine, which will be used to perform all of the file manipulations.<placeholder-2/> We can now view the file systems in the image using the <placeholder-3/> command:<placeholder-4/>We need to mount the logical volume that contains the root partition: <placeholder-5/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:78(para)
#: ./doc/image-guide/ch_modifying_images.xml:82(para)
msgid "Next, we want to delete a file. We can use the <placeholder-1/> guestfish command, which works the same way it does in a traditional shell."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:82(para)
#: ./doc/image-guide/ch_modifying_images.xml:86(para)
msgid "<placeholder-1/>We want to edit the <filename>ifcfg-eth0</filename> file to remove the <literal>HWADDR</literal> line. The <placeholder-2/> command will copy the file to the host, invoke your editor, and then copy the file back. <placeholder-3/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:89(para)
#: ./doc/image-guide/ch_modifying_images.xml:93(para)
msgid "If you want to modify this image to load the 8021q kernel at boot time, you must create an executable script in the <filename>/etc/sysconfig/modules/</filename> directory. You can use the <placeholder-1/> guestfish command to create an empty file, the <placeholder-2/> command to edit it, and the <placeholder-3/> command to make it executable.<placeholder-4/> We add the following line to the file and save it:<placeholder-5/>Then we set to executable: <placeholder-6/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:103(para)
#: ./doc/image-guide/ch_modifying_images.xml:107(para)
msgid "We're done, so we can exit using the <placeholder-1/> command:<placeholder-2/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:108(title)
#: ./doc/image-guide/ch_modifying_images.xml:112(title)
msgid "Go further with guestfish"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:109(para)
#: ./doc/image-guide/ch_modifying_images.xml:113(para)
msgid "There is an enormous amount of functionality in guestfish and a full treatment is beyond the scope of this document. Instead, we recommend that you read the <link href=\"http://libguestfs.org/guestfs-recipes.1.html\">guestfs-recipes</link> documentation page for a sense of what is possible with these tools."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:119(title)
#: ./doc/image-guide/ch_modifying_images.xml:123(title)
msgid "guestmount"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:120(para)
#: ./doc/image-guide/ch_modifying_images.xml:124(para)
msgid "For some types of changes, you may find it easier to mount the image's file system directly in the guest. The <placeholder-1/> program, also from the libguestfs project, allows you to do so."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:124(para)
#: ./doc/image-guide/ch_modifying_images.xml:128(para)
msgid "For example, to mount the root partition from our <filename>centos63_desktop.qcow2</filename> image to <filename>/mnt</filename>, we can do:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:130(para)
#: ./doc/image-guide/ch_modifying_images.xml:134(para)
msgid "If we didn't know in advance what the mount point is in the guest, we could use the <literal>-i</literal>(inspect) flag to tell guestmount to automatically determine what mount point to use:<placeholder-1/>Once mounted, we could do things like list the installed packages using rpm:<placeholder-2/> Once done, we unmount:<placeholder-3/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:142(title)
#: ./doc/image-guide/ch_modifying_images.xml:146(title)
msgid "virt-* tools"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:147(para)
#: ./doc/image-guide/ch_modifying_images.xml:151(para)
msgid "<link href=\"http://libguestfs.org/virt-edit.1.html\">virt-edit</link> for editing a file inside of an image."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:153(para)
#: ./doc/image-guide/ch_modifying_images.xml:157(para)
msgid "<link href=\"http://libguestfs.org/virt-df.1.html\">virt-df</link> for displaying free space inside of an image."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:159(para)
#: ./doc/image-guide/ch_modifying_images.xml:163(para)
msgid "<link href=\"http://libguestfs.org/virt-resize.1.html\">virt-resize</link> for resizing an image."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:165(para)
#: ./doc/image-guide/ch_modifying_images.xml:169(para)
msgid "<link href=\"http://libguestfs.org/virt-sysprep.1.html\">virt-sysprep</link> for preparing an image for distribution (for example, delete SSH host keys, remove MAC address info, or remove user accounts)."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:173(para)
#: ./doc/image-guide/ch_modifying_images.xml:177(para)
msgid "<link href=\"http://libguestfs.org/virt-sparsify.1.html\">virt-sparsify</link> for making an image sparse"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:179(para)
#: ./doc/image-guide/ch_modifying_images.xml:183(para)
msgid "<link href=\"http://libguestfs.org/virt-v2v/\">virt-p2v</link> for converting a physical machine to an image that runs on KVM"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:185(para)
#: ./doc/image-guide/ch_modifying_images.xml:189(para)
msgid "<link href=\"http://libguestfs.org/virt-v2v/\">virt-v2v</link> for converting Xen and VMWare images to KVM images"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:143(para)
#: ./doc/image-guide/ch_modifying_images.xml:147(para)
msgid "The <link href=\"http://libguestfs.org/\">libguestfs</link> project has a number of other useful tools, including:<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:192(title)
#: ./doc/image-guide/ch_modifying_images.xml:196(title)
msgid "Modify a single file inside of an image"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:193(para)
#: ./doc/image-guide/ch_modifying_images.xml:197(para)
msgid "This example shows how to use <placeholder-1/> to modify a file. The command can take either a filename as an argument with the <literal>-a</literal> flag, or a domain name as an argument with the <literal>-d</literal> flag. The following examples shows how to use this to modify the <filename>/etc/shadow</filename> file in instance with libvirt domain name <literal>instance-000000e1</literal> that is currently running:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:210(title)
#: ./doc/image-guide/ch_modifying_images.xml:214(title)
msgid "Resize an image"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:211(para)
msgid "Here's a simple of example of how to use <placeholder-1/> to resize an image. Assume we have a 16GB Windows image in qcow2 format that we want to resize to 50GB. First, we use <placeholder-2/> to identify the partitions:<placeholder-3/>"
#: ./doc/image-guide/ch_modifying_images.xml:215(para)
msgid "Here's a simple of example of how to use <placeholder-1/> to resize an image. Assume we have a 16 GB Windows image in qcow2 format that we want to resize to 50 GB. First, we use <placeholder-2/> to identify the partitions:<placeholder-3/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:223(para)
#: ./doc/image-guide/ch_modifying_images.xml:227(para)
msgid "In this case, it's the <filename>/dev/sda2</filename> partition that we want to resize. We create a new qcow2 image and use the <placeholder-1/> command to write a resized copy of the original into the new image: <placeholder-2/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:257(title)
#: ./doc/image-guide/ch_modifying_images.xml:261(title)
msgid "Loop devices, kpartx, network block devices"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:261(para)
#: ./doc/image-guide/ch_modifying_images.xml:265(para)
msgid "Mounting untrusted guest images using the tools described in this section is a security risk, always use libguestfs tools such as guestfish and guestmount if you have access to them. See <link href=\"https://www.berrange.com/posts/2013/02/20/a-reminder-why-you-should-never-mount-guest-disk-images-on-the-host-os/\">A reminder why you should never mount guest disk images on the host OS</link> by Daniel Berrangé for more details."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:258(para)
#: ./doc/image-guide/ch_modifying_images.xml:262(para)
msgid "If you don't have access to libguestfs, you can mount image file systems directly in the host using loop devices, kpartx, and network block devices.<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:271(title)
#: ./doc/image-guide/ch_modifying_images.xml:275(title)
msgid "Mount a raw image (without LVM)"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:272(para)
#: ./doc/image-guide/ch_modifying_images.xml:276(para)
msgid "If you have a raw virtual machine image that is not using LVM to manage its partitions. First, use the <placeholder-1/> command to find an unused loop device. <placeholder-2/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:278(para)
#: ./doc/image-guide/ch_modifying_images.xml:282(para)
msgid "In this example, <filename>/dev/loop0</filename> is free. Associate a loop device with the raw image:<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:281(para)
#: ./doc/image-guide/ch_modifying_images.xml:285(para)
msgid "If the image only has a single partition, you can mount the loop device directly:<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:284(para)
#: ./doc/image-guide/ch_modifying_images.xml:288(para)
msgid "If the image has multiple partitions, use <placeholder-1/> to expose the partitions as separate devices (for example, <filename>/dev/mapper/loop0p1</filename>), then mount the partition that corresponds to the root file system:<placeholder-2/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:290(para)
#: ./doc/image-guide/ch_modifying_images.xml:294(para)
msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created per partition:<placeholder-1/>To mount the second partition, as root:<placeholder-2/>Once you're done, to clean up:<placeholder-3/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:305(title)
#: ./doc/image-guide/ch_modifying_images.xml:309(title)
msgid "Mount a raw image (with LVM)"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:306(para)
#: ./doc/image-guide/ch_modifying_images.xml:310(para)
msgid "If your partitions are managed with LVM, use losetup and kpartx as in the previous example to expose the partitions to the host:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:313(para)
#: ./doc/image-guide/ch_modifying_images.xml:317(para)
msgid "Next, you need to use the <placeholder-1/> command to identify the LVM volume groups and then <placeholder-2/> to expose the volumes as devices:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:323(para)
#: ./doc/image-guide/ch_modifying_images.xml:327(para)
msgid "Clean up when you're done:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:330(title)
#: ./doc/image-guide/ch_modifying_images.xml:334(title)
msgid "Mount a qcow2 image (without LVM)"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:331(para)
#: ./doc/image-guide/ch_modifying_images.xml:335(para)
msgid "You need the <literal>nbd</literal> (network block device) kernel module loaded to mount qcow2 images. This will load it with support for 16 block devices, which is fine for our purposes. As root:<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:336(para)
#: ./doc/image-guide/ch_modifying_images.xml:340(para)
msgid "Assuming the first block device (<filename>/dev/nbd0</filename>) is not currently in use, we can expose the disk partitions using the <placeholder-1/> and <placeholder-2/> commands. As root:<placeholder-3/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:343(para)
#: ./doc/image-guide/ch_modifying_images.xml:347(para)
msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created for each partition:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:352(para)
#: ./doc/image-guide/ch_modifying_images.xml:356(para)
msgid "If the network block device you selected was already in use, the initial <placeholder-1/> command will fail silently, and the <filename>/dev/nbd3p{1,2,3}</filename> device files will not be created."
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:359(para)
#: ./doc/image-guide/ch_modifying_images.xml:363(para)
msgid "If the image partitions are not managed with LVM, they can be mounted directly:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:363(para)
#: ./doc/image-guide/ch_modifying_images.xml:367(para)
msgid "When you're done, clean up:"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:368(title)
#: ./doc/image-guide/ch_modifying_images.xml:372(title)
msgid "Mount a qcow2 image (with LVM)"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:369(para)
#: ./doc/image-guide/ch_modifying_images.xml:373(para)
msgid "If the image partitions are managed with LVM, after you use <placeholder-1/> and <placeholder-2/>, you must use <placeholder-3/> and <placeholder-4/> in order to expose the LVM partitions as devices that can be mounted:<placeholder-5/>"
msgstr ""
#: ./doc/image-guide/ch_modifying_images.xml:383(para)
#: ./doc/image-guide/ch_modifying_images.xml:387(para)
msgid "When you're done, clean up:<placeholder-1/>"
msgstr ""
@ -1441,107 +1441,107 @@ 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:78(None)
#: ./doc/image-guide/ch_creating_images_manually.xml:82(None)
msgid "@@image: 'figures/virt-manager-new.png'; md5=3528ebfc1b945b7dd80a34897b8fe98e"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:6(title)
#: ./doc/image-guide/ch_creating_images_manually.xml:10(title)
msgid "Create images manually"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:7(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:11(para)
msgid "Creating a new image is a step done outside of your OpenStack installation. You create the new image manually on your own system and then upload the image to your cloud."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:11(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:15(para)
msgid "To create a new image, you will need the installation CD or DVD ISO file for the guest operating system. You'll also need access to a virtualization tool. You can use KVM for this. Or, if you have a GUI desktop virtualization tool (such as, VMWare Fusion and VirtualBox), you can use that instead and just convert the file to raw once you're done."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:17(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:21(para)
msgid "When you create a new virtual machine image, you will need to connect to the graphical console of the hypervisor, which acts as the virtual machine's display and allows you to interact with the guest operating system's installer using your keyboard and mouse. KVM can expose the graphical console using the <link href=\"https://en.wikipedia.org/wiki/Virtual_Network_Computing\">VNC</link> (Virtual Network Computing) protocol or the newer <link href=\"http://spice-space.org\">SPICE</link> protocol. We'll use the VNC protocol here, since you're more likely to be able to find a VNC client that works on your local desktop."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:30(title)
#: ./doc/image-guide/ch_creating_images_manually.xml:34(title)
msgid "Verify the libvirt default network is running"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:31(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:35(para)
msgid "Before starting a virtual machine with libvirt, verify that the libvirt \"default\" network has been started. This network must be active for your virtual machine to be able to connect out to the network. Starting this network will create a Linux bridge (usually called <literal>virbr0</literal>), iptables rules, and a dnsmasq process that will serve as a DHCP server."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:38(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:42(para)
msgid "To verify that the libvirt \"default\" network is enabled, use the <placeholder-1/> command and verify that the \"default\" network is active:"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:45(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:49(para)
msgid "If the network is not active, start it by doing:"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:49(title)
#: ./doc/image-guide/ch_creating_images_manually.xml:53(title)
msgid "Use the virt-manager X11 GUI"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:50(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:54(para)
msgid "If you plan to create a virtual machine image on a machine that can run X11 applications, the simplest way to do so is to use the <placeholder-1/> GUI, which is installable as the <literal>virt-manager</literal> package on both Fedora-based and Debian-based systems. This GUI has an embedded VNC client in it that will let you view and interact with the guest's graphical console."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:58(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:62(para)
msgid "If you are building the image on a headless server, and you have an X server on your local machine, you can launch <placeholder-1/>  using ssh X11 forwarding to access the GUI. Since virt-manager interacts directly with libvirt, you typically need to be root to access it. If you can ssh directly in as root (or with a user that has permissions to interact with libvirt), do:<placeholder-2/>"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:69(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:73(para)
msgid "The <literal>-X</literal> flag passed to ssh will enable X11 forwarding over ssh. If this does not work, try replacing it with the <literal>-Y</literal> flag."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:66(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:70(para)
msgid "If the account you use to ssh into your server does not have permissions to run libvirt, but has sudo privileges, do:<placeholder-1/><placeholder-2/>"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:74(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:78(para)
msgid "Click the \"New\" button at the top-left and step through the instructions. <placeholder-1/>You will be shown a series of dialog boxes that will allow you to specify information about the virtual machine."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:83(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:87(para)
msgid "When using qcow2 format images you should check the option 'customize before install', go to disk properties and explicitly select the qcow2 format. This ensures the virtual machine disk size will be correct."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:91(title)
#: ./doc/image-guide/ch_creating_images_manually.xml:95(title)
msgid "Use virt-install and connect by using a local VNC client"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:93(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:97(para)
msgid "If you do not wish to use virt-manager (for example, you do not want to install the dependencies on your server, you don't have an X server running locally, the X11 forwarding over SSH isn't working), you can use the <placeholder-1/> tool to boot the virtual machine through libvirt and connect to the graphical console from a VNC client installed on your local machine."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:101(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:105(para)
msgid "Because VNC is a standard protocol, there are multiple clients available that implement the VNC spec, including <link href=\"http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Welcome_to_TigerVNC\">TigerVNC</link> (multiple platforms), <link href=\"http://tightvnc.com/\">TightVNC</link> (multiple platforms), <link href=\"http://realvnc.com/\">RealVNC</link> (multiple platforms), <link href=\"http://sourceforge.net/projects/chicken/\">Chicken</link> (Mac OS X), <link href=\"http://userbase.kde.org/Krdc\">Krde</link> (KDE), and <link href=\"http://projects.gnome.org/vinagre/\">Vinagre</link> (GNOME)."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:116(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:120(para)
msgid "The following example shows how to use the <placeholder-1/> command to create an empty image file <placeholder-2/> command to start up a virtual machine using that image file. As root:"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:148(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:154(para)
msgid "When using the libvirt <literal>default</literal> network, libvirt will connect the virtual machine's interface to a bridge called <literal>virbr0</literal>. There is a dnsmasq process managed by libvirt that will hand out an IP address on the 192.168.122.0/24 subnet, and libvirt has iptables rules for doing NAT for IP addresses on this subnet."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:133(para)
msgid "This uses the KVM hypervisor to start up a virtual machine with the libvirt name of <literal>centos-6.4</literal> with 1024MB of RAM, with a virtual CD-ROM drive associated with the <filename>/data/CentOS-6.4-x86_64-netinstall.iso</filename> file, and a local hard disk which is stored in the host at <filename>/data/centos-6.4.qcow2</filename> that is 10GB in size in qcow2 format. It configures networking to use libvirt's default network. There is a VNC server that is listening on all interfaces, and libvirt will not attempt to launch a VNC client automatically nor try to display the text console (<literal>--no-autoconsole</literal>). Finally, libvirt will attempt to optimize the configuration for a Linux guest running a RHEL 6.x distribution.<placeholder-1/>"
#: ./doc/image-guide/ch_creating_images_manually.xml:137(para)
msgid "The KVM hypervisor starts the virtual machine with the libvirt name, <literal>centos-6.4</literal>, with 1024 MB of RAM. The virtual machine also has a virtual CD-ROM drive associated with the <filename>/data/CentOS-6.4-x86_64-netinstall.iso</filename> file and a local 10 GB hard disk in qcow2 format that is stored in the host at <filename>/data/centos-6.4.qcow2</filename>. It configures networking to use libvirt's default network. There is a VNC server that is listening on all interfaces, and libvirt will not attempt to launch a VNC client automatically nor try to display the text console (<literal>--no-autoconsole</literal>). Finally, libvirt will attempt to optimize the configuration for a Linux guest running a RHEL 6.x distribution.<placeholder-1/>"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:157(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:163(para)
msgid "Run the <placeholder-1/> command to see a range of allowed <literal>--os-variant</literal> options."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:161(replaceable)
#: ./doc/image-guide/ch_creating_images_manually.xml:167(replaceable)
msgid "vm-name"
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:160(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:166(para)
msgid "Use the <placeholder-1/> command to get the VNC port number."
msgstr ""
#: ./doc/image-guide/ch_creating_images_manually.xml:165(para)
#: ./doc/image-guide/ch_creating_images_manually.xml:171(para)
msgid "In the example above, the guest <literal>centos-6.4</literal> uses VNC display <literal>:1</literal>, which corresponds to tcp port <literal>5901</literal>. You should be able to connect to a VNC client running on your local machine to display :1 on the remote machine and step through the installation process."
msgstr ""

132
doc/install-guide/locale/install-guide.pot
View File

File diff suppressed because one or more lines are too long

2
doc/security-guide/locale/security-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-03-20 06:23+0000\n"
"POT-Creation-Date: 2014-03-21 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

502
doc/training-guides/locale/training-guides.pot
View File

File diff suppressed because it is too large Load Diff

108
doc/user-guide-admin/locale/user-guide-admin.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-03-20 06:23+0000\n"
"POT-Creation-Date: 2014-03-21 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -145,7 +145,7 @@ msgstr ""
msgid "Name for the new flavor."
msgstr ""
#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:29(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:36(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:172(guilabel) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:138(para)
#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:29(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:36(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:172(guilabel) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:139(para)
msgid "VCPUs"
msgstr ""
@ -1537,7 +1537,7 @@ msgstr ""
msgid "Property name"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:18(th) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:41(th)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:18(th) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:42(th)
msgid "Defines the number of"
msgstr ""
@ -1609,7 +1609,7 @@ msgstr ""
msgid "NewValue"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:40(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:43(replaceable)
msgid "tenantID"
msgstr ""
@ -1869,195 +1869,195 @@ msgstr ""
msgid "You cannot undo this action."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:14(title)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:15(title)
msgid "View and manage quotas"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:15(para) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:15(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:16(para) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:16(para)
msgid "To prevent system capacities from being exhausted without notification, you can set up quotas. Quotas are operational limits. For example, the number of gigabytes allowed for each tenant can be controlled so that cloud resources are optimized. Quotas can be enforced at both the tenant (or project) and the tenant-user level."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:20(para)
msgid "Typically, you change quotas when a project needs more than 10 volumes or 1 TB on a compute node."
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:21(para)
msgid "Typically, you change quotas when a project needs more than ten volumes or 1 TB on a compute node."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:22(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:23(para)
msgid "Using the Dashboard, you can view default Compute and Block Storage quotas for new tenants, as well as update quotas for existing tenants."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:25(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:26(para)
msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service (see <xref linkend=\"cli_set_quotas\"/>). Additionally, you can update Compute service quotas for tenant users."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:31(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:32(para)
msgid "The following table describes the Compute and Block Storage service quotas:"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:34(caption)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:35(caption)
msgid "Quota Descriptions"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:40(th)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:41(th)
msgid "Quota Name"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:42(th)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:43(th)
msgid "Service"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:48(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:49(para)
msgid "Gigabytes"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:51(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:52(para)
msgid "Volume gigabytes allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:53(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:134(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:152(td)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:54(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:135(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:153(td)
msgid "Block Storage"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:57(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:58(para)
msgid "Instances"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:60(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:61(para)
msgid "Instances allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:62(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:71(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:80(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:89(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:98(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:107(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:116(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:125(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:143(td)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:63(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:72(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:81(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:90(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:99(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:108(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:117(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:126(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:144(td)
msgid "Compute"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:66(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:67(para)
msgid "Injected Files"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:69(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:70(para)
msgid "Injected files allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:75(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:76(para)
msgid "Injected File Content Bytes"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:78(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:79(para)
msgid "Content bytes allowed for each injected file."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:84(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:85(para)
msgid "Keypairs"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:87(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:88(para)
msgid "Number of keypairs."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:93(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:94(para)
msgid "Metadata Items"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:96(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:97(para)
msgid "Metadata items allowed for each instance."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:102(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:103(para)
msgid "RAM (MB)"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:105(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:106(para)
msgid "RAM megabytes allowed for each instance."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:111(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:112(para)
msgid "Security Groups"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:114(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:115(para)
msgid "Security groups allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:120(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:121(para)
msgid "Security Group Rules"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:123(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:124(para)
msgid "Rules allowed for each security group."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:129(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:130(para)
msgid "Snapshots"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:132(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:133(para)
msgid "Volume snapshots allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:141(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:142(para)
msgid "Instance cores allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:147(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:148(para)
msgid "Volumes"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:150(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:151(para)
msgid "Volumes allowed for each project."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:157(title)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:158(title)
msgid "View default project quotas"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:160(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:178(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:161(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:179(para)
msgid "Log in to the OpenStack dashboard."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:163(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:181(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:164(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:182(para)
msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Defaults</guilabel> category."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:167(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:168(para)
msgid "The default quota values are displayed."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:171(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:172(para)
msgid "You can sort the table by clicking on either the <guilabel>Quota Name</guilabel> or <guilabel>Limit</guilabel> column headers."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:175(title)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:176(title)
msgid "Update project quotas"
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:185(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:191(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:186(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:192(para)
msgid "Click the <guibutton>Update Defaults</guibutton> button."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:188(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:189(para)
msgid "In the <guilabel>Update Default Quotas</guilabel> window, you can edit the default quota values."
msgstr ""
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:195(para)
#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:196(para)
msgid "The dashboard does not show all possible project quotas. To view and update the quotas for a service, use its command-line client. See <xref linkend=\"cli_set_quotas\"/>."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:14(title)
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:15(title)
msgid "Manage quotas"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:21(para)
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:22(para)
msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:24(para)
msgid "Typically, default values are changed because a tenant requires more than 10 volumes, or more than 1 TB on a compute node."
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:25(para)
msgid "The cloud operator typically changes default values because a tenant requires more than ten volumes or 1 TB on a compute node."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:27(para)
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:30(para)
msgid "To view all tenants (projects), run: <placeholder-1/>"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:38(para)
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:41(para)
msgid "To display all current users for a tenant, run:"
msgstr ""

98
doc/user-guide/locale/user-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-03-20 06:23+0000\n"
"POT-Creation-Date: 2014-03-21 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -985,191 +985,191 @@ msgstr ""
msgid "To download an object from a container:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:6(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:10(title)
msgid "Store metadata on a configuration drive"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:7(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:11(para)
msgid "You can configure OpenStack to write metadata to a special configuration drive that attaches to the instance when it boots. The instance can mount this drive and read files from it to get information that is normally available through the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">metadata service</link>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:14(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:18(para)
msgid "One use case for the configuration drive is to pass a networking configuration when you do not use DHCP to assign IP addresses to instances. For example, you might pass the IP configuration for the instance through the configuration drive, which the instance can mount and access before you configure the network settings for the instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:20(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:24(para)
msgid "Any modern guest operating system that is capable of mounting an ISO9660 or VFAT file system can use the configuration drive."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:24(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:28(title)
msgid "Requirements and guidelines"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:26(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:30(title)
msgid "Compute host requirements"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:28(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:32(para)
msgid "The following hypervisors support the configuration drive: libvirt, xenserver, hyper-v, and vmware."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:33(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:37(para)
msgid "To use configuration drive with libvirt, xenserver, or vmware, you must first install the <package>genisoimage</package> package on each compute host. Otherwise, instances do not boot properly."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:39(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:43(para)
msgid "Use the <literal>mkisofs_cmd</literal> flag to set the path where you install the <package>genisoimage</package> program. If <package>genisoimage</package> is in same path as the <systemitem class=\"service\">nova-compute</systemitem> service, you do not need to set this flag."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:47(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:51(para)
msgid "By default, Ubuntu packages do not install this package. See bug <link href=\"https://bugs.launchpad.net/cloud-archive/+bug/1165174\">#1165174</link>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:54(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:58(para)
msgid "To use configuration drive with hyper-v, you must set the <literal>mkisofs_cmd</literal> value to the full path to an <literal>mkisofs.exe</literal> installation. Additionally, you must set the <literal>qemu_img_cmd</literal> value in the <literal>hyperv</literal> configuration section to the full path to an <literal>qemu-img</literal> command installation."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:67(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:71(title)
msgid "Image requirements"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:69(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:73(para)
msgid "An image built with a recent version of the <package>cloud-init</package> package can automatically access metadata passed through the configuration drive. The <package>cloud-init</package> package version 0.7.1 works with Ubuntu and Fedora-based images, such as RHEL."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:78(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:82(para)
msgid "If an image does not have the <package>cloud-init</package> package installed, you must customize the image to run a script that mounts the configuration drive on boot, reads the data from the drive, and takes appropriate action such as adding the public key to an account. See <xref linkend=\"config_drive_contents\"/> for details on how data is organized on the configuration drive."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:90(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:94(para)
msgid "If you use Xen with a configuration drive, use the <literal>xenapi_disable_agent</literal> configuration parameter to disable the agent."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:97(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:101(title)
msgid "Guidelines"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:99(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:103(para)
msgid "Do not rely on the presence of the EC2 metadata present in the configuration drive, as this content might be removed in a future release. For example, do not rely on files in the <filename>ec2</filename> directory."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:106(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:110(para)
msgid "When you create images that access configuration drive data and multiple directories are under the <filename>openstack</filename> directory, always select the highest API version by date that your consumer supports. For example, if your guest image supports the 2012-03-05, 2012-08-05, 2013-04-13 versions, try 2013-04-13 first and fall back to a previous version if 2013-04-13 is not present."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:119(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:123(title)
msgid "Enable and access the configuration drive"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:122(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:126(para)
msgid "To enable the configuration drive, pass the <literal>--config-drive=true</literal> parameter to the <placeholder-1/> command."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:126(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:130(para)
msgid "This example enables the configuration drive and passes user data, two files, and two key/value metadata pairs, all of which are accessible from the configuration drive:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:131(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:135(para)
msgid "You can also configure the Compute service to always create a configuration drive."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:133(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:137(para)
msgid "Set this option in the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:138(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:142(para)
msgid "If a user passes the <parameter>--config-drive=true</parameter> flag to the <placeholder-1/> command, an administrator cannot disable the configuration drive."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:146(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:150(para)
msgid "The configuration drive has the <literal>config-2</literal> volume label. If your guest operating system supports accessing disk by label, you can mount the configuration drive as the <filename>/dev/disk/by-label/config-2</filename> device."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:153(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:157(para)
msgid "For example:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:157(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:161(para)
msgid "Make sure that you use at least version 0.3.1 of CirrOS for configuration drive support."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:160(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:164(para)
msgid "If your guest operating system does not use <literal>udev</literal>, the <filename>/dev/disk/by-label</filename> directory is not present."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:164(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:168(para)
msgid "You can use the <placeholder-1/> command to identify the block device that corresponds to the configuration drive. For example, when you boot the CirrOS image with the <literal>m1.tiny</literal> flavor, the device is <filename>/dev/vdb</filename>:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:172(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:176(para)
msgid "Once identified, you can mount the device:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:179(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:183(title)
msgid "Configuration drive contents"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:180(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:184(para)
msgid "In this example, the contents of the configuration drive are:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:193(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:197(para)
msgid "The files that appear on the configuration drive depend on the arguments that you pass to the <placeholder-1/> command."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:198(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:202(title)
msgid "OpenStack metadata format"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:199(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:203(para)
msgid "The following example shows the contents of the <filename>openstack/2012-08-10/meta_data.json</filename> and <filename>openstack/latest/meta_data.json</filename> files. These files are identical. The file contents are formatted for readability:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:206(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:210(para)
msgid "Note the effect of the <literal>--file /etc/network/interfaces=/home/myuser/instance-interfaces</literal> argument that was passed to the <placeholder-1/> command. The contents of this file are contained in the <filename>openstack/content/0000</filename> file on the configuration drive, and the path is specified as <filename>/etc/network/interfaces</filename> in the <filename>meta_data.json</filename> file."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:217(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:221(title)
msgid "EC2 metadata format"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:218(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:222(para)
msgid "The following example shows the contents of the <filename>ec2/2009-04-04/meta-data.json</filename>, <filename>latest/meta-data.json</filename> files. These files are identical. The file contents are formatted to improve readability:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:226(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:230(title)
msgid "User data"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:227(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:231(para)
msgid "The <filename>openstack/2012-08-10/user_data</filename>, <filename>openstack/latest/user_data</filename>, <filename>ec2/2009-04-04/user-data</filename>, and <filename>ec2/latest/user-data</filename> file are present only if the <literal>--user-data</literal> flag and the contents of the user data file are passed to the <placeholder-1/> command."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:237(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:241(title)
msgid "Configuration drive format"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:238(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:242(para)
msgid "The default format of the configuration drive as an ISO 9660 file system. To explicitly specify the ISO 9660 format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:244(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:248(para)
msgid "By default, you cannot attach the configuration drive image as a CD drive instead of as a disk drive. To attach a CD drive, add this line to the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:250(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:254(para)
msgid "For legacy reasons, you can configure the configuration drive to use VFAT format instead of ISO 9660. It is unlikely that you would require VFAT format because ISO 9660 is widely supported across operating systems. However, to use the VFAT format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:259(para)
msgid "If you choose VFAT, the configuration drive is 64 MBs."
#: ./doc/user-guide/section_cli_nova_config-drive.xml:263(para)
msgid "If you choose VFAT, the configuration drive is 64 MB."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:264(title)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:268(title)
msgid "Configuration drive reference"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:265(para)
#: ./doc/user-guide/section_cli_nova_config-drive.xml:269(para)
msgid "The following table shows the configuration options for the configuration drive:"
msgstr ""