openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: I8a16fe82b02982f8ce0cd1a25153b183b9e35ab7
This commit is contained in:
OpenStack Proposal Bot
2015-01-22 06:15:41 +00:00
parent 72e0a45bb0
commit 5383f92545
10 changed files with 6714 additions and 8020 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-01-21 06:12+0000\n"
"POT-Creation-Date: 2015-01-22 06:14+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"
@@ -1187,7 +1187,7 @@ msgid "For tenants, you can use quota controls to limit the:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:146(para)
msgid "Number of volumes that may be launched."
msgid "Number of volumes that can be launched."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:149(para)
@@ -1235,198 +1235,198 @@ msgid "Persistent volumes are created by users and their size is limited only by
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:223(para)
msgid "You can configure persistent volumes as bootable and use them to provide a persistent virtual instance similar to traditional non-cloud-based virtualization systems. Typically, the resulting instance can also still have ephemeral storage depending on the flavor selected, but the root file system can be on the persistent volume and its state maintained even if the instance is shut down. For more information about this type of configuration, see the <link href=\"http://docs.openstack.org/juno/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
msgid "You can configure persistent volumes as bootable and use them to provide a persistent virtual instance similar to traditional non-cloud-based virtualization systems. It is still possible for the resulting instance to also have ephemeral storage, depending on the flavor selected. In this case, the root file system can be on the persistent volume and its state maintained even if the instance is shut down. For more information about this type of configuration, see the <link href=\"http://docs.openstack.org/juno/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:233(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:236(para)
msgid "Persistent volumes do not provide concurrent access from multiple instances. That type of configuration requires a traditional network file system like NFS or CIFS, or a cluster file system such as GlusterFS. These systems can be built within an OpenStack cluster or provisioned outside of it, but OpenStack software does not provide these features."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:243(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:246(title)
msgid "EC2 compatibility API"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:244(para)
msgid "In addition to the native compute API, OpenStack provides an EC2-compatible API. This API allows EC2 legacy workflows built for EC2 to work with OpenStack. The <link href=\"http://docs.openstack.org/juno/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> lists configuration options for customizing this compatibility API on your OpenStack cloud."
#: ./doc/admin-guide-cloud/ch_compute.xml:247(para)
msgid "In addition to the native compute API, OpenStack provides an EC2-compatible API. This API allows EC2 legacy workflows built for EC2 to work with OpenStack. For more information and configuration options about this compatibility API, see the <link href=\"http://docs.openstack.org/juno/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:251(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:254(para)
msgid "Numerous third-party tools and language-specific SDKs can be used to interact with OpenStack clouds, using both native and compatibility APIs. Some of the more popular third-party tools are:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:257(term)
#: ./doc/admin-guide-cloud/ch_compute.xml:260(term)
msgid "Euca2ools"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:259(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:262(para)
msgid "A popular open source command-line tool for interacting with the EC2 API. This is convenient for multi-cloud environments where EC2 is the common API, or for transitioning from EC2-based clouds to OpenStack. For more information, see the <link href=\"http://open.eucalyptus.com/wiki/Euca2oolsGuide\">euca2ools site</link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:270(term)
#: ./doc/admin-guide-cloud/ch_compute.xml:273(term)
msgid "Hybridfox"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:272(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:275(para)
msgid "A Firefox browser add-on that provides a graphical interface to many popular public and private cloud technologies, including OpenStack. For more information, see the <link href=\"http://code.google.com/p/hybridfox/\"> hybridfox site</link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:281(term)
#: ./doc/admin-guide-cloud/ch_compute.xml:284(term)
msgid "boto"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:283(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:286(para)
msgid "A Python library for interacting with Amazon Web Services. It can be used to access OpenStack through the EC2 compatibility API. For more information, see the <link href=\"https://github.com/boto/boto\"> boto project page on GitHub</link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:292(term)
#: ./doc/admin-guide-cloud/ch_compute.xml:295(term)
msgid "fog"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:294(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:297(para)
msgid "A Ruby cloud services library. It provides methods for interacting with a large number of cloud and virtualization platforms, including OpenStack. For more information, see the <link href=\"https://rubygems.org/gems/fog\"> fog site</link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:303(term)
#: ./doc/admin-guide-cloud/ch_compute.xml:306(term)
msgid "php-opencloud"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:305(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:308(para)
msgid "A PHP SDK designed to work with most OpenStack- based cloud deployments, as well as Rackspace public cloud. For more information, see the <link href=\"http://www.php-opencloud.com\"> php-opencloud site</link>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:316(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:319(title)
msgid "Building blocks"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:317(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:320(para)
msgid "In OpenStack the base operating system is usually copied from an image stored in the OpenStack Image Service. This is the most common case and results in an ephemeral instance that starts from a known template state and loses all accumulated states on virtual machine deletion. It is also possible to put an operating system on a persistent volume in the Cinder volume system. This gives a more traditional persistent system that accumulates states, which are preserved on the Cinder volume across the deletion and re-creation of the virtual machine. To get a list of available images on your system run: <placeholder-1/>"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:337(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:24(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:340(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:24(para)
msgid "The displayed image attributes are:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:340(literal) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:27(literal) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:522(replaceable)
#: ./doc/admin-guide-cloud/ch_compute.xml:343(literal) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:27(literal) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:522(replaceable)
msgid "ID"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:342(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:345(para)
msgid "Automatically generated UUID of the image"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:347(literal) ./doc/admin-guide-cloud/blockstorage/section_ts_eql_volume_size.xml:111(entry) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:33(literal)
#: ./doc/admin-guide-cloud/ch_compute.xml:350(literal) ./doc/admin-guide-cloud/blockstorage/section_ts_eql_volume_size.xml:111(entry) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:33(literal)
msgid "Name"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:349(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:352(para)
msgid "Free form, human-readable name for image"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:354(literal) ./doc/admin-guide-cloud/blockstorage/section_ts_eql_volume_size.xml:112(entry) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:39(literal)
#: ./doc/admin-guide-cloud/ch_compute.xml:357(literal) ./doc/admin-guide-cloud/blockstorage/section_ts_eql_volume_size.xml:112(entry) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:39(literal)
msgid "Status"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:356(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:41(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:359(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:41(para)
msgid "The status of the image. Images marked <literal>ACTIVE</literal> are available for use."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:362(literal) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:47(literal)
#: ./doc/admin-guide-cloud/ch_compute.xml:365(literal) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:47(literal)
msgid "Server"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:364(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:49(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:367(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:49(para)
msgid "For images that are created as snapshots of running instances, this is the UUID of the instance the snapshot derives from. For uploaded images, this field is blank."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:371(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:374(para)
msgid "Virtual hardware templates are called <literal>flavors</literal>. The default installation provides five flavors. By default, these are configurable by admin users, however that behavior can be changed by redefining the access controls for <parameter>compute_extension:flavormanage</parameter> in <filename>/etc/nova/policy.json</filename> on the <filename>compute-api</filename> server."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:379(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:382(para)
msgid "For a list of flavors that are available on your system:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:394(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:397(title)
msgid "Compute service architecture"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:395(para)
msgid "The following basic categories describe the service architecture and what's going on within the cloud controller."
#: ./doc/admin-guide-cloud/ch_compute.xml:398(para)
msgid "These basic categories describe the service architecture and information about the cloud controller."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:398(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:401(title)
msgid "API server"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:399(para)
msgid "At the heart of the cloud framework is an API server. This API server makes command and control of the hypervisor, storage, and networking programmatically available to users."
#: ./doc/admin-guide-cloud/ch_compute.xml:402(para)
msgid "At the heart of the cloud framework is an API server, which makes command and control of the hypervisor, storage, and networking programmatically available to users."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:402(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:405(para)
msgid "The API endpoints are basic HTTP web services which handle authentication, authorization, and basic command and control functions using various API interfaces under the Amazon, Rackspace, and related models. This enables API compatibility with multiple existing tool sets created for interaction with offerings from other vendors. This broad compatibility prevents vendor lock-in."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:413(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:416(title)
msgid "Message queue"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:414(para)
msgid "A messaging queue brokers the interaction between compute nodes (processing), the networking controllers (software which controls network infrastructure), API endpoints, the scheduler (determines which physical hardware to allocate to a virtual resource), and similar components. Communication to and from the cloud controller is by HTTP requests through multiple API endpoints."
#: ./doc/admin-guide-cloud/ch_compute.xml:417(para)
msgid "A messaging queue brokers the interaction between compute nodes (processing), the networking controllers (software which controls network infrastructure), API endpoints, the scheduler (determines which physical hardware to allocate to a virtual resource), and similar components. Communication to and from the cloud controller is handled by HTTP requests through multiple API endpoints."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:423(para)
msgid "A typical message passing event begins with the API server receiving a request from a user. The API server authenticates the user and ensures that the user is permitted to issue the subject command. The availability of objects implicated in the request is evaluated and, if available, the request is routed to the queuing engine for the relevant workers. Workers continually listen to the queue based on their role, and occasionally their type host name. When an applicable work request arrives on the queue, the worker takes assignment of the task and begins its execution. Upon completion, a response is dispatched to the queue which is received by the API server and relayed to the originating user. Database entries are queried, added, or removed as necessary throughout the process."
#: ./doc/admin-guide-cloud/ch_compute.xml:426(para)
msgid "A typical message passing event begins with the API server receiving a request from a user. The API server authenticates the user and ensures that they are permitted to issue the subject command. The availability of objects implicated in the request is evaluated and, if available, the request is routed to the queuing engine for the relevant workers. Workers continually listen to the queue based on their role, and occasionally their type host name. When an applicable work request arrives on the queue, the worker takes assignment of the task and begins executing it. Upon completion, a response is dispatched to the queue which is received by the API server and relayed to the originating user. Database entries are queried, added, or removed as necessary during the process."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:435(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:442(title)
msgid "Compute worker"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:436(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:443(para)
msgid "Compute workers manage computing instances on host machines. The API dispatches commands to compute workers to complete these tasks:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:441(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:448(para)
msgid "Run instances"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:444(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:451(para)
msgid "Terminate instances"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:447(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:454(para)
msgid "Reboot instances"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:450(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:457(para)
msgid "Attach volumes"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:453(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:460(para)
msgid "Detach volumes"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:456(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:463(para)
msgid "Get console output"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:461(title)
#: ./doc/admin-guide-cloud/ch_compute.xml:468(title)
msgid "Network Controller"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:462(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:469(para)
msgid "The Network Controller manages the networking resources on host machines. The API server dispatches commands through the message queue, which are subsequently processed by Network Controllers. Specific operations include:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:469(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:476(para)
msgid "Allocate fixed IP addresses"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:472(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:479(para)
msgid "Configuring VLANs for projects"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:475(para)
#: ./doc/admin-guide-cloud/ch_compute.xml:482(para)
msgid "Configuring networks for compute nodes"
msgstr ""
@@ -2008,7 +2008,7 @@ msgstr ""
msgid "Libvirt (KVM/QEMU)"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:536(th) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:240(title)
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:536(th) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:292(title)
msgid "XenServer"
msgstr ""
@@ -4284,7 +4284,7 @@ msgstr ""
msgid "Terminate traffic on a specific VLAN from a NSX gateway service:"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1358(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:44(replaceable)
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1358(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:54(replaceable)
msgid "VLAN_ID"
msgstr ""
@@ -10663,58 +10663,62 @@ msgid "Configure Compute to use IPv6 addresses"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:5(para)
msgid "If you are using OpenStack Compute with <systemitem>nova-network</systemitem>, you can put Compute into IPv4/IPv6 dual-stack mode, so that it uses both IPv4 and IPv6 addresses for communication. In IPv4/IPv6 dual-stack mode, instances can acquire their IPv6 global unicast address by using a stateless address auto configuration mechanism [RFC 4862/2462]. IPv4/IPv6 dual-stack mode works with both <literal>VlanManager</literal> and <literal>FlatDHCPManager</literal> networking modes. In <literal>VlanManager</literal>, each project uses a different 64-bit global routing prefix. In <literal>FlatDHCPManager</literal>, all instances use one 64-bit global routing prefix."
msgid "If you are using OpenStack Compute with <systemitem>nova-network</systemitem>, you can put Compute into dual-stack mode, so that it uses both IPv4 and IPv6 addresses for communication. In dual-stack mode, instances can acquire their IPv6 global unicast address by using a stateless address auto-configuration mechanism [RFC 4862/2462]. IPv4/IPv6 dual-stack mode works with both <literal>VlanManager</literal> and <literal>FlatDHCPManager</literal> networking modes."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:13(para)
msgid "This configuration was tested with VM images that have an IPv6 stateless address auto configuration capability. This capability is required for any VM you want to run with an IPv6 address. You must use EUI-64 address for stateless address auto configuration. Each node that executes a <literal>nova-*</literal> service must have <literal>python-netaddr</literal> and <literal>radvd</literal> installed."
msgid "In <literal>VlanManager</literal> networking mode, each project uses a different 64-bit global routing prefix. In <literal>FlatDHCPManager</literal> mode, all instances use one 64-bit global routing prefix."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:19(title)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:18(para)
msgid "This configuration was tested with virtual machine images that have an IPv6 stateless address auto-configuration capability. This capability is required for any VM to run with an IPv6 address. You must use an EUI-64 address for stateless address auto-configuration. Each node that executes a <literal>nova-*</literal> service must have <literal>python-netaddr</literal> and <literal>radvd</literal> installed."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:26(title)
msgid "Switch into IPv4/IPv6 dual-stack mode"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:21(para)
msgid "On all nodes running a <literal>nova-*</literal> service, install <systemitem>python-netaddr</systemitem>:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:28(para)
msgid "For every node running a <literal>nova-*</literal> service, install <systemitem>python-netaddr</systemitem>:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:26(para)
msgid "On all <literal>nova-network</literal> nodes, install <literal>radvd</literal> and configure IPv6 networking:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:34(para)
msgid "For every node running <literal>nova-network</literal>, install <literal>radvd</literal> and configure IPv6 networking:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:33(para)
msgid "Edit the <filename>nova.conf</filename> file on all nodes to specify <literal>use_ipv6 = True</literal>."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:42(para)
msgid "On all nodes, edit the <filename>nova.conf</filename> file and specify <literal>use_ipv6 = True</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:37(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:46(para)
msgid "Restart all <literal>nova-*</literal> services."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:41(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:50(para)
msgid "You can add a fixed range for IPv6 addresses to the <placeholder-1/> command. Specify <placeholder-2/> or <placeholder-3/> after the <placeholder-4/> parameter."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:44(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:54(replaceable)
msgid "FIXED_RANGE_V4"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:44(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:54(replaceable)
msgid "VPN_START"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:44(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:54(replaceable)
msgid "FIXED_RANGE_V6"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:45(para)
msgid "You can set IPv6 global routing prefix by using the <parameter>--fixed_range_v6</parameter> parameter. The default value for the parameter is <literal>fd00::/48</literal>."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:55(para)
msgid "You can set the IPv6 global routing prefix by using the <parameter>--fixed_range_v6</parameter> parameter. The default value for the parameter is <literal>fd00::/48</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:49(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:59(para)
msgid "When you use <literal>FlatDHCPManager</literal>, the command uses the original <parameter>--fixed_range_v6</parameter> value. For example:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:54(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:64(para)
msgid "When you use <literal>VlanManager</literal>, the command increments the subnet ID to create subnet prefixes. Guest VMs use this prefix to generate their IPv6 global unicast address. For example:"
msgstr ""
@@ -11088,7 +11092,7 @@ msgstr ""
msgid "Lists the floating IP addresses in the pool."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:485(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:281(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:485(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:344(replaceable)
msgid "POOL_NAME"
msgstr ""
@@ -12054,292 +12058,284 @@ msgstr ""
msgid "Only cloud administrators can perform live migrations. If your cloud is configured to use cells, you can perform live migration within but not between cells."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:10(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:12(para)
msgid "Migration enables an administrator to move a virtual-machine instance from one compute host to another. This feature is useful when a compute host requires maintenance. Migration can also be useful to redistribute the load when many VM instances are running on a specific physical machine."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:14(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:17(para)
msgid "The migration types are:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:17(para)
msgid "<emphasis role=\"bold\">Migration</emphasis> (or non-live migration). The instance is shut down (and the instance knows that it was rebooted) for a period of time to be moved to another hypervisor."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:20(para)
msgid "<emphasis role=\"bold\">Non-live migration</emphasis> (sometimes referred to simply as 'migration'). The instance is shut down for a period of time to be moved to another hypervisor. In this case, the instance recognizes that it was rebooted."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:22(para)
msgid "<emphasis role=\"bold\">Live migration</emphasis> (or true live migration). Almost no instance downtime. Useful when the instances must be kept running during the migration. The types of <firstterm>live migration</firstterm> are:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:26(para)
msgid "<emphasis role=\"bold\">Live migration</emphasis> (or 'true live migration'). Almost no instance downtime. Useful when the instances must be kept running during the migration. The different types of live migration are:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:27(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:33(para)
msgid "<emphasis role=\"bold\">Shared storage-based live migration</emphasis>. Both hypervisors have access to shared storage."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:31(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:37(para)
msgid "<emphasis role=\"bold\">Block live migration</emphasis>. No shared storage is required. Incompatible with read-only devices such as CD-ROMs and <link href=\"http://docs.openstack.org/user-guide/content/config-drive.html\">Configuration Drive (config_drive)</link>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:37(para)
msgid "<emphasis role=\"bold\">Volume-backed live migration</emphasis>. When instances are backed by volumes rather than ephemeral disk, no shared storage is required, and migration is supported (currently only in libvirt-based hypervisors)."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:44(para)
msgid "The following sections describe how to configure your hosts and compute nodes for migrations by using the KVM and XenServer hypervisors."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:47(title)
msgid "KVM-Libvirt"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:49(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:244(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:306(title)
msgid "Prerequisites"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:51(para)
msgid "<emphasis role=\"bold\">Hypervisor:</emphasis> KVM with libvirt"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:45(para)
msgid "<emphasis role=\"bold\">Volume-backed live migration</emphasis>. Instances are backed by volumes rather than ephemeral disk, no shared storage is required, and migration is supported (currently only available for libvirt-based hypervisors)."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:54(para)
msgid "<emphasis role=\"bold\">Shared storage:</emphasis><filename><replaceable>NOVA-INST-DIR</replaceable>/instances/</filename> (for example, <filename>/var/lib/nova/instances</filename>) has to be mounted by shared storage. This guide uses NFS but other options, including the <link href=\"http://gluster.org/community/documentation//index.php/OSConnect\">OpenStack Gluster Connector</link> are available."
msgid "The following sections describe how to configure your hosts and compute nodes for migrations by using the KVM and XenServer hypervisors."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:58(title)
msgid "KVM-Libvirt"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:60(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:296(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:370(title)
msgid "Prerequisites"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:62(para)
msgid "<emphasis role=\"bold\">Instances:</emphasis> Instance can be migrated with iSCSI based volumes"
msgid "<emphasis role=\"bold\">Hypervisor:</emphasis> KVM with libvirt"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:69(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:65(para)
msgid "<emphasis role=\"bold\">Shared storage:</emphasis><filename><replaceable>NOVA-INST-DIR</replaceable>/instances/</filename> (for example, <filename>/var/lib/nova/instances</filename>) has to be mounted by shared storage. This guide uses NFS but other options, including the <link href=\"http://gluster.org/community/documentation//index.php/OSConnect\"> OpenStack Gluster Connector</link> are available."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:75(para)
msgid "<emphasis role=\"bold\">Instances:</emphasis> Instance can be migrated with iSCSI-based volumes."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:83(para)
msgid "Because the Compute service does not use the libvirt live migration functionality by default, guests are suspended before migration and might experience several minutes of downtime. For details, see <xref linkend=\"true-live-migration-kvm-libvirt\"/>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:74(para)
msgid "This guide assumes the default value for <placeholder-1/> in your <filename>nova.conf</filename> file (<filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename>). If you have changed the <literal>state_path</literal> or <literal>instances_path</literal> variables, modify accordingly."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:90(para)
msgid "This guide assumes the default value for <placeholder-1/> in your <filename>nova.conf</filename> file (<filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename>). If you have changed the <literal>state_path</literal> or <literal>instances_path</literal> variables, modify the commands accordingly."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:81(para)
msgid "You must specify <literal>vncserver_listen=0.0.0.0</literal> or live migration does not work correctly."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:98(para)
msgid "You must specify <literal>vncserver_listen=0.0.0.0</literal> or live migration will not work correctly."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:87(title)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:105(title)
msgid "Example Compute installation environment"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:90(para)
msgid "Prepare at least three servers; for example, <literal>HostA</literal>, <literal>HostB</literal>, and <literal>HostC</literal>:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:108(para)
msgid "Prepare at least three servers. In this example, we refer to the servers as <literal>HostA</literal>, <literal>HostB</literal>, and <literal>HostC</literal>:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:94(para)
msgid "<literal>HostA</literal> is the <firstterm baseform=\"cloud controller\">Cloud Controller</firstterm>, and should run these services: <systemitem class=\"service\">nova-api</systemitem>, <systemitem class=\"service\">nova-scheduler</systemitem>, <literal>nova-network</literal>, <systemitem class=\"service\">cinder-volume</systemitem>, and <literal>nova-objectstore</literal>."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:113(para)
msgid "<literal>HostA</literal> is the <firstterm baseform=\"cloud controller\">Cloud Controller</firstterm>, and should run these services: <systemitem class=\"service\"> nova-api</systemitem>, <systemitem class=\"service\">nova-scheduler</systemitem>, <literal>nova-network</literal>, <systemitem class=\"service\"> cinder-volume</systemitem>, and <literal>nova-objectstore</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:101(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:122(para)
msgid "<literal>HostB</literal> and <literal>HostC</literal> are the <firstterm baseform=\"compute node\">compute nodes</firstterm> that run <systemitem class=\"service\">nova-compute</systemitem>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:106(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:128(para)
msgid "Ensure that <literal><replaceable>NOVA-INST-DIR</replaceable></literal> (set with <literal>state_path</literal> in the <filename>nova.conf</filename> file) is the same on all hosts."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:111(para)
msgid "In this example, <literal>HostA</literal> is the NFSv4 server that exports <filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename> directory. <literal>HostB</literal> and <literal>HostC</literal> are NFSv4 clients that mount it."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:134(para)
msgid "In this example, <literal>HostA</literal> is the NFSv4 server that exports <filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename> directory. <literal>HostB</literal> and <literal>HostC</literal> are NFSv4 clients that mount <literal>HostA</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:118(title)
msgid "To configure your system"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:141(title)
msgid "Configuring your system"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:120(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:143(para)
msgid "Configure your DNS or <filename>/etc/hosts</filename> and ensure it is consistent across all hosts. Make sure that the three hosts can perform name resolution with each other. As a test, use the <placeholder-1/> command to ping each host from one another."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:129(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:155(para)
msgid "Ensure that the UID and GID of your Compute and libvirt users are identical between each of your servers. This ensures that the permissions on the NFS mount works correctly."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:134(para)
msgid "Export <filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename> from <literal>HostA</literal>, and have it readable and writable by the Compute user on <literal>HostB</literal> and <literal>HostC</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:137(para)
msgid "For more information, see: <link href=\"https://help.ubuntu.com/community/SettingUpNFSHowTo\">SettingUpNFSHowTo</link> or <link href=\"http://www.cyberciti.biz/faq/centos-fedora-rhel-nfs-v4-configuration/\">CentOS / Red Hat: Setup NFS v4.0 File Server</link>"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:144(para)
msgid "Configure the NFS server at <literal>HostA</literal> by adding the following line to the <filename>/etc/exports</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:146(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:158(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:163(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:169(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:173(replaceable)
msgid "NOVA-INST-DIR"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:147(para)
msgid "Change the subnet mask (<literal>255.255.0.0</literal>) to the appropriate value to include the IP addresses of <literal>HostB</literal> and <literal>HostC</literal>. Then restart the NFS server:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:154(para)
msgid "Set the 'execute/search' bit on your shared directory."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:155(para)
msgid "On both compute nodes, make sure to enable the 'execute/search' bit to allow qemu to be able to use the images within the directories. On all hosts, run the following command:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:161(para)
msgid "Configure NFS at HostB and HostC by adding the following line to the <filename>/etc/fstab</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:164(para)
msgid "Ensure that you can mount the exported directory can be mounted:"
msgid "Export <filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename> from <literal>HostA</literal>, and ensure it is readable and writable by the Compute user on <literal>HostB</literal> and <literal>HostC</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:166(para)
msgid "Check that HostA can see the \"<filename><replaceable>NOVA-INST-DIR</replaceable>/instances/</filename>\" directory:"
msgid "For more information, see: <link href=\"https://help.ubuntu.com/community/SettingUpNFSHowTo\">SettingUpNFSHowTo</link> or <link href=\"http://www.cyberciti.biz/faq/centos-fedora-rhel-nfs-v4-configuration/\">CentOS/Red Hat: Setup NFS v4.0 File Server</link>"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:169(filename) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:173(filename)
msgid "<placeholder-1/>/instances/"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:173(para)
msgid "Configure the NFS server at <literal>HostA</literal> by adding the following line to the <filename>/etc/exports</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:171(para)
msgid "Perform the same check at HostB and HostC, paying special attention to the permissions (Compute should be able to write):"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:176(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:189(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:196(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:204(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:210(replaceable)
msgid "NOVA-INST-DIR"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:186(para)
msgid "Update the libvirt configurations so that the calls can be made securely. These methods enable remote access over TCP and are not documented here. Please consult your network administrator for assistance in deciding how to configure access."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:177(para)
msgid "Change the subnet mask (<literal>255.255.0.0</literal>) to the appropriate value to include the IP addresses of <literal>HostB</literal> and <literal>HostC</literal>. Then restart the NFS server:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:191(para)
msgid "SSH tunnel to libvirtd's UNIX socket"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:185(para)
msgid "On both compute nodes, enable the 'execute/search' bit on your shared directory to allow qemu to be able to use the images within the directories. On all hosts, run the following command:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:194(para)
msgid "libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:192(para)
msgid "Configure NFS on <literal>HostB</literal> and <literal>HostC</literal> by adding the following line to the <filename>/etc/fstab</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:197(para)
msgid "libvirtd TCP socket, with TLS for encryption and x509 client certs for authentication"
msgid "Ensure that you can mount the exported directory:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:201(para)
msgid "libvirtd TCP socket, with TLS for encryption and Kerberos for authentication"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:200(para)
msgid "Check that <literal>HostA</literal> can see the <filename><replaceable>NOVA-INST-DIR</replaceable>/instances/</filename>\" directory:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:205(para)
msgid "Restart libvirt. After you run the command, ensure that libvirt is successfully restarted:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:204(filename) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:210(filename)
msgid "<placeholder-1/>/instances/"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:212(para)
msgid "Configure your firewall to allow libvirt to communicate between nodes."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:206(para)
msgid "Perform the same check on <literal>HostB</literal> and <literal>HostC</literal>, paying special attention to the permissions (Compute should be able to write):"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:213(para)
msgid "By default, libvirt listens on TCP port 16509, and an ephemeral TCP range from 49152 to 49261 is used for the KVM communications. Based on the secure remote access TCP configuration you chose, be careful choosing what ports you open and understand who has access. For information about ports that are used with libvirt, see <link href=\"http://libvirt.org/remote.html#Remote_libvirtd_configuration\">the libvirt documentation</link>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:221(para)
msgid "You can now configure options for live migration. In most cases, you do not need to configure any options. The following chart is for advanced usage only."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:228(title)
msgid "Enable true live migration"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:223(para)
msgid "Update the libvirt configurations so that the calls can be made securely. These methods enable remote access over TCP and are not documented here."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:229(para)
msgid "By default, the Compute service does not use the libvirt live migration functionality. To enable this functionality, add the following line to the <filename>nova.conf</filename> file:"
msgid "SSH tunnel to libvirtd's UNIX socket"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:233(para)
msgid "The Compute service does not use libvirt's live migration by default because there is a risk that the migration process never ends. This can happen if the guest operating system dirties blocks on the disk faster than they can be migrated."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:232(para)
msgid "libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:242(title)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:237(para)
msgid "libvirtd TCP socket, with TLS for encryption and x509 client certs for authentication"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:242(para)
msgid "libvirtd TCP socket, with TLS for encryption and Kerberos for authentication"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:247(para)
msgid "Restart libvirt. After you run the command, ensure that libvirt is successfully restarted:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:255(para)
msgid "Configure your firewall to allow libvirt to communicate between nodes."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:258(para)
msgid "By default, libvirt listens on TCP port 16509, and an ephemeral TCP range from 49152 to 49261 is used for the KVM communications. Based on the secure remote access TCP configuration you chose, be careful which ports you open, and always understand who has access. For information about ports that are used with libvirt, see <link href=\"http://libvirt.org/remote.html#Remote_libvirtd_configuration\"> the libvirt documentation</link>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:268(para)
msgid "You can now configure options for live migration. In most cases, you will not need to configure any options. The following chart is for advanced users only."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:277(title)
msgid "Enabling true live migration"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:278(para)
msgid "By default, the Compute service does not use the libvirt live migration function. To enable this function, add the following line to the <filename>nova.conf</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:283(para)
msgid "The Compute service does not use libvirt's live migration by default because there is a risk that the migration process will never end. This can happen if the guest operating system uses blocks on the disk faster than they can be migrated."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:294(title)
msgid "Shared storage"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:246(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:298(para)
msgid "<emphasis role=\"bold\">Compatible XenServer hypervisors</emphasis>. For more information, see the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/reference.html#pooling_homogeneity_requirements\">Requirements for Creating Resource Pools</link> section of the <citetitle>XenServer Administrator's Guide</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:253(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:306(para)
msgid "<emphasis role=\"bold\">Shared storage</emphasis>. An NFS export, visible to all XenServer hosts."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:256(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:310(para)
msgid "For the supported NFS versions, see the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/reference.html#id1002701\">NFS VHD</link> section of the <citetitle>XenServer Administrator's Guide</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:263(para)
msgid "To use shared storage live migration with XenServer hypervisors, the hosts must be joined to a XenServer pool. To create that pool, a host aggregate must be created with special metadata. This metadata is used by the XAPI plug-ins to establish the pool."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:318(para)
msgid "To use shared storage live migration with XenServer hypervisors, the hosts must be joined to a XenServer pool. To create that pool, a host aggregate must be created with specific metadata. This metadata is used by the XAPI plugins to establish the pool."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:267(title)
msgid "To use shared storage live migration with XenServer hypervisors"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:324(title)
msgid "Using shared storage live migration with XenServer hypervisors"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:269(para)
msgid "Add an NFS VHD storage to your master XenServer, and set it as default SR. For more information, see NFS VHD in the <citetitle>XenServer Administrator's Guide</citetitle>."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:326(para)
msgid "Add an NFS VHD storage to your master XenServer, and set it as the default storage repository. For more information, see NFS VHD in the <citetitle>XenServer Administrator's Guide</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:274(para)
msgid "Configure all compute nodes to use the default <literal>sr</literal> for pool operations. Add this line to your <filename>nova.conf</filename> configuration files across your compute nodes:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:332(para)
msgid "Configure all compute nodes to use the default storage repository (<literal>sr</literal>) for pool operations. Add this line to your <filename>nova.conf</filename> configuration files on all compute nodes:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:280(para)
msgid "Create a host aggregate:"
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:340(para)
msgid "Create a host aggregate. This command creates the aggregate, and then displays a table that contains the ID of the new aggregate:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:281(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:344(replaceable)
msgid "AVAILABILITY_ZONE"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:282(para)
msgid "The command displays a table that contains the ID of the newly created aggregate."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:345(para)
msgid "Add metadata to the aggregate, to mark it as a hypervisor pool:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:284(para)
msgid "Now add special metadata to the aggregate, to mark it as a hypervisor pool:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:285(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:286(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:288(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:293(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:348(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:349(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:351(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:356(replaceable)
msgid "AGGREGATE_ID"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:287(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:350(para)
msgid "Make the first compute node part of that aggregate:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:288(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:351(replaceable)
msgid "MASTER_COMPUTE_NAME"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:289(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:352(para)
msgid "The host is now part of a XenServer pool."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:292(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:355(para)
msgid "Add hosts to the pool:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:293(replaceable)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:356(replaceable)
msgid "COMPUTE_HOST_NAME"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:295(para)
msgid "At this point, the added compute node and the host are shut down, to join the host to the XenServer pool. The operation fails, if any server other than the compute node is running/suspended on your host."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:358(para)
msgid "The added compute node and the host will shut down to join the host to the XenServer pool. The operation will fail if any server other than the compute node is running or suspended on the host."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:304(title)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:368(title)
msgid "Block migration"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:308(para)
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:372(para)
msgid "<emphasis role=\"bold\">Compatible XenServer hypervisors</emphasis>. The hypervisors must support the Storage XenMotion feature. See your XenServer manual to make sure your edition has this feature."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:316(para)
msgid "To use block migration, you must use the CHANGE THIS == <parameter>==block-migrate</parameter> parameter with the live migration command."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:381(para)
msgid "To use block migration, you must use the <parameter>==block-migrate</parameter> parameter with the live migration command."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:321(para)
msgid "Block migration works only with EXT local storage SRs, and the server must not have any volumes attached."
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:387(para)
msgid "Block migration works only with EXT local storage storage repositories, and the server must not have any volumes attached."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:4(title)

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

File diff suppressed because one or more lines are too long

5397
doc/common/locale/fr.po
View File

File diff suppressed because it is too large Load Diff

5347
doc/common/locale/ja.po
View File

File diff suppressed because it is too large Load Diff

64
doc/install-guide/locale/ko_KR.po
View File

@@ -17,9 +17,9 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-01-20 20:43+0000\n"
"PO-Revision-Date: 2015-01-20 18:33+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"POT-Creation-Date: 2015-01-22 05:45+0000\n"
"PO-Revision-Date: 2015-01-22 01:41+0000\n"
"Last-Translator: Hak-Geon, Lee <withteas@gmail.com>\n"
"Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -1284,7 +1284,7 @@ msgstr "요구되는 패키지들을 설치가 필요합니다. 현재, sahara
#: ./doc/install-guide/section_sahara-install.xml39(para)
msgid "Edit <filename>/etc/sahara/sahara.conf</filename> configuration file"
msgstr ""
msgstr "<filename>/etc/sahara/sahara.conf</filename> 설정 파일을 수정합니다"
#: ./doc/install-guide/section_sahara-install.xml45(replaceable)
msgid "SAHARA_DBPASS"
@@ -1416,7 +1416,7 @@ msgstr "검증 과정"
#: ./doc/install-guide/section_dashboard-verify.xml9(para)
msgid "This section describes how to verify operation of the dashboard."
msgstr ""
msgstr "이 섹션에서는 대시보드의 동작을 확인하는 법을 설명합니다."
#: ./doc/install-guide/section_dashboard-verify.xml13(para)
msgid ""
@@ -1438,7 +1438,7 @@ msgid ""
"This section describes how to verify operation of the Image Service using "
"<link href=\"http://launchpad.net/cirros\">CirrOS</link>, a small Linux "
"image that helps you test your OpenStack deployment."
msgstr ""
msgstr "이 섹션에서는 이미지 서비스의 동작을 <link href=\"http://launchpad.net/cirros\">CirrOS</link> 라는 오픈스택 배포 테스트를 도와주는 작은 리눅스 이미지를 이용하여 확인하는 방법을 설명합니다."
#: ./doc/install-guide/section_glance-verify.xml12(para)
msgid ""
@@ -1707,7 +1707,7 @@ msgstr "노드의 호스트네임을 <code><replaceable>controller</replaceable>
#: ./doc/install-guide/section_basics-networking-nova.xml167(para)
msgid ""
"Edit the <filename>/etc/hosts</filename> file to contain the following:"
msgstr ""
msgstr "<filename>/etc/hosts</filename> 파일을 다음을 포함하도록 수정합니다:"
#: ./doc/install-guide/section_basics-networking-neutron.xml115(para)
#: ./doc/install-guide/section_basics-networking-neutron.xml195(para)
@@ -1754,7 +1754,7 @@ msgstr "<replaceable>INTERFACE_NAME</replaceable> 을 실제 interface 이름으
msgid ""
"Edit the <filename>/etc/network/interfaces</filename> file to contain the "
"following:"
msgstr ""
msgstr "<filename>/etc/network/interfaces</filename> 파일을 다음을 포함하도록 수정합니다:"
#: ./doc/install-guide/section_basics-networking-neutron.xml149(replaceable)
#: ./doc/install-guide/section_basics-networking-neutron.xml150(replaceable)
@@ -1775,7 +1775,7 @@ msgid ""
"Edit the <filename>/etc/sysconfig/network-"
"scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to "
"contain the following:"
msgstr ""
msgstr "<filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> 파일을 다음을 포함하도록 수정합니다:"
#: ./doc/install-guide/section_basics-networking-neutron.xml158(para)
#: ./doc/install-guide/section_basics-networking-nova.xml141(para)
@@ -1790,7 +1790,7 @@ msgid ""
"Edit the "
"<filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename>"
" file to contain the following:"
msgstr ""
msgstr "<filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> 파일을 다음을 포함하도록 수정합니다:"
#: ./doc/install-guide/section_basics-networking-neutron.xml181(para)
msgid "Set the hostname of the node to <code>network</code>."
@@ -2163,7 +2163,7 @@ msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml8(para)
msgid ""
"This section describes how to verify operation of the Identity service."
msgstr ""
msgstr "이 섹션에서는 Identity 서비스의 동작을 확인하는 방법을 설명합니다."
#: ./doc/install-guide/section_keystone-verify.xml12(para)
msgid ""
@@ -2544,7 +2544,7 @@ msgid ""
"(iSCSI)\">iSCSI</glossterm> transport. You can follow these instructions "
"with minor modifications to horizontally scale your environment with "
"additional storage nodes."
msgstr ""
msgstr "이 섹션에서는 스토리지 노드들에 블록스토리지 서비스를 설치하고 설정하는 방법을 설명합니다. 간단히 하기 위해, 이 설정은 하나의 스토리지 노드에 하나의 블록 스토리지 장치<literal>/dev/sdb</literal>가 전체 장치를 차지하고 있는 하나의 파티션 <literal>/dev/sdb1</literal> 라는 적절한 파티션 테이블에 가지고 있는 것을 참고합니다. 이 서비스는 장치의 <glossterm>LVM</glossterm> 을 이용한 논리적 볼륨들을 프로비젼하고, 그 것들을 <glossterm baseform=\"Internet Small Computer Systems Interface (iSCSI)\">iSCSI</glossterm> 통신을 통하여 인스턴스들에게 제공합니다. 이 명령어들을 약간 수정하여 따라하면 추가 스토리지 노드들을 이용하여 환경의 수평확장을 할수 있습니다."
#: ./doc/install-guide/section_cinder-storage-node.xml22(para)
msgid ""
@@ -2866,7 +2866,7 @@ msgstr "<code>seen true</code> 옵션은 사용자가 본 지정 화면을 더
msgid ""
"This section describes how to verify operation of the Orchestration module "
"(heat)."
msgstr ""
msgstr "이 섹션에서는 Orchestration 모듈(heat)의 동작을 확인하는 방법을 설명합니다."
#: ./doc/install-guide/section_heat-verify.xml12(para)
#: ./doc/install-guide/section_launch-instance-nova.xml16(para)
@@ -2915,7 +2915,7 @@ msgid ""
"This section describes how to install and configure the Block Storage "
"service, code-named cinder, on the controller node. This service requires at"
" least one additional storage node that provides volumes to instances."
msgstr ""
msgstr "이 섹션에서는 코드네임 cinder라 불리는 블록 스토리지 서비스를 컨트롤러 노드에 설치하고 설정하는 방법을 설명합니다. 이 서비스는 볼륨을 인스턴스에 재공할 최소한 한대의 추가 노드를 요구합니다."
#: ./doc/install-guide/section_cinder-controller-node.xml14(para)
msgid ""
@@ -3087,7 +3087,7 @@ msgstr ""
msgid ""
"Edit the <filename>/etc/ntp.conf</filename> file and add, change, or remove "
"the following keys as necessary for your environment:"
msgstr ""
msgstr "<filename>/etc/ntp.conf</filename> 파일을 수정하고 환경에 필요한 다음 키들을 추가,변경 또는 제거합니다:"
#: ./doc/install-guide/section_basics-ntp.xml34(replaceable)
msgid "NTP_SERVER"
@@ -3152,7 +3152,7 @@ msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml118(para)
#: ./doc/install-guide/section_basics-ntp.xml133(para)
msgid "Run this command on the <emphasis>controller</emphasis> node:"
msgstr ""
msgstr "이 명령어를 <emphasis>controller</emphasis> 노드에서 실행합니다:"
#: ./doc/install-guide/section_basics-ntp.xml125(para)
msgid ""
@@ -3412,7 +3412,7 @@ msgstr "tenant 라우터 게이트웨이에 ping을 확인합니다:"
msgid ""
"This section describes how to install and configure the Compute service, "
"code-named nova, on the controller node."
msgstr ""
msgstr "이 섹션에서는 코드네임 nova라 불리는 Compute 서비스를 컨트롤러 노드에 설치하고 설정하는 방법을 설명합니다."
#: ./doc/install-guide/section_nova-controller-install.xml12(para)
msgid ""
@@ -3958,7 +3958,7 @@ msgstr "서비스를 시작하고 시스템 부팅시 시작하도록 설정합
#: ./doc/install-guide/section_nova-verify.xml8(para)
msgid "This section describes how to verify operation of the Compute service."
msgstr ""
msgstr "이 섹션에서는 Compute 서비스의 동작을 확인하는 방법을 설명합니다."
#: ./doc/install-guide/section_nova-verify.xml20(para)
#: ./doc/install-guide/section_cinder-verify.xml23(para)
@@ -3991,7 +3991,7 @@ msgid ""
"This section describes how to install and configure the Image Service, code-"
"named glance, on the controller node. For simplicity, this configuration "
"stores images on the local file system."
msgstr ""
msgstr "이 섹션에서는 코드네임 glance라 불리는 이미지 서비스를 컨트롤러 노드에 설치하고 설정하는 방법을 설명합니다. 간단히 하기위해, 이 설정은 로컬 파일 시스템에 이미지를 저장합니다."
#: ./doc/install-guide/section_glance-install.xml12(para)
msgid ""
@@ -4123,7 +4123,7 @@ msgstr "이미지 서비스를 시작하고 시스템 부팅시 시작하도록
msgid ""
"This section describes how to install and configure the dashboard on the "
"controller node."
msgstr "이 섹션에서는 컨트롤러 노드에 대시보드를 설치하고 설정하는 방법을 서술합니다."
msgstr "이 섹션에서는 컨트롤러 노드에 대시보드를 설치하고 설정하는 방법을 설명합니다."
#: ./doc/install-guide/section_dashboard-install.xml11(para)
msgid ""
@@ -4377,7 +4377,7 @@ msgstr ""
msgid ""
"Edit the <filename>/etc/sysctl.conf</filename> file to contain the following"
" parameters:"
msgstr ""
msgstr "<filename>/etc/sysctl.conf</filename> 파일을 다음 매개변수를 포함하도록 수정합니다:"
#: ./doc/install-guide/section_neutron-compute-node.xml22(para)
#: ./doc/install-guide/section_neutron-network-node.xml22(para)
@@ -4666,7 +4666,7 @@ msgstr ""
msgid ""
"This section describes how to verify operation of the Block Storage service "
"by creating a volume."
msgstr ""
msgstr "이 섹션에서는 볼륨을 만드는 것을 통해 블록 스토리지 서비스의 동작을 확인하는 방법을 설명합니다."
#: ./doc/install-guide/section_cinder-verify.xml10(para)
msgid ""
@@ -5198,7 +5198,7 @@ msgstr ""
msgid ""
"Edit the <filename>admin-openrc.sh</filename> file and add the following "
"content:"
msgstr ""
msgstr "<filename>admin-openrc.sh</filename> 파일을 수정하고 다음 내용을 추가합니다:"
#: ./doc/install-guide/section_keystone-openrc.xml28(para)
msgid ""
@@ -5210,7 +5210,7 @@ msgstr "<literal>ADMIN_PASS</literal> 를 Identity 서비스에서 <literal>admi
msgid ""
"Edit the <filename>demo-openrc.sh</filename> file and add the following "
"content:"
msgstr ""
msgstr "<filename>demo-openrc.sh</filename> 파일을 수정하고 다음 내용을 추가합니다:"
#: ./doc/install-guide/section_keystone-openrc.xml38(para)
msgid ""
@@ -5943,7 +5943,7 @@ msgid ""
"machines. On legacy hardware, this configuration uses the generic QEMU "
"hypervisor. You can follow these instructions with minor modifications to "
"horizontally scale your environment with additional compute nodes."
msgstr ""
msgstr "이 섹션에서는 Compute 서비스를 compute 노드에 설치하고 설정하는 방법을 설명합니다. 이 서비스는 여러 <glossterm baseform=\"hypervisor\">hypervisors</glossterm> 에 <glossterm baseform=\"instance\">instances</glossterm> 또는 <glossterm baseform=\"virtual machine (VM)\">VMs</glossterm> 를 배포하는 것을 지원합니다. 간단히 하기위해, 이 설정은 <glossterm baseform=\"Quick EMUlator (QEMU)\">QEMU</glossterm> 하이퍼바이저를 <glossterm baseform=\"kernel-based VM (KVM)\">KVM</glossterm> 확장기능과 함께 virtual machine의 하드웨어 가속이 지원되는 compute 노드에서 사용합니다. 레거시 하드웨어에서는, 이 설정은 일반 QEMU 하이퍼바이저를 사용합니다. 이 명령어들을 약간 수정하여 따라하면 추가 compute 노드들을 이용하여 환경의 수평확장을 할수 있습니다."
#: ./doc/install-guide/section_nova-compute-install.xml22(para)
msgid ""
@@ -6337,7 +6337,7 @@ msgstr "Orchestration 설치와 설정"
msgid ""
"This section describes how to install and configure the Orchestration "
"module, code-named heat, on the controller node."
msgstr ""
msgstr "이 섹션에서는 코드네임 heat라 불리는 Orchestration 모듈을 컨트롤러 노드에 설치하고 설정하는 방법을 설명합니다."
#: ./doc/install-guide/section_heat-install.xml12(para)
msgid ""
@@ -6883,7 +6883,7 @@ msgid ""
"code-named ceilometer, on the controller node. The Telemetry module uses "
"separate agents to collect measurements from each OpenStack service in your "
"environment."
msgstr ""
msgstr "이 섹션에서는 코드네임 ceilometer라 불리는 Telemetry 모듈을 컨트롤러 노드에 설치하고 설정하는 법을 설명합니다. Telemetry 모듈은 환경 내의 각 오픈스택 서비스에서 측정값을 모으는 개별 에이전트를 사용합니다."
#: ./doc/install-guide/section_ceilometer-controller.xml18(para)
msgid ""
@@ -7865,7 +7865,7 @@ msgid ""
"horizontally scaling your environment, see the <link "
"href=\"http://docs.openstack.org/developer/swift/deployment_guide.html\">Deployment"
" Guide</link>."
msgstr ""
msgstr "이 섹션에서는 계정, 컨테이너, 오브젝트 서비스들을 작동할 스토리지 노드들을 설치하고 설정하는 방법을 설명한다. 간단히 하기위해, 이 설정은 각각 두개의 빈 로컬 블록 스토리지 장치가 있는 두 스토리지 노드들을 참고합니다. 각 장치들,<literal>/dev/sdb</literal> 와 <literal>/dev/sdc</literal>, 는 한 개의 파티션이 모든 장치를 차지하고 있는 적절한 파티션 테이블을 가지고 있어야만 합니다. 비록 오브젝트 스토리지 서비스가 <glossterm>extended attributes (xattr)</glossterm>와 함께 어떠한 파일 시스템도 지원하지만, 테스트와 벤치마킹에서 <glossterm>XFS</glossterm> 상에서 최고의 성능과 신뢰성을 나타냈습니다. 환경의 수평확장에 대한 더 많은 정보를 위해서는, <link href=\"http://docs.openstack.org/developer/swift/deployment_guide.html\">Deployment Guide</link>를 보십시오."
#: ./doc/install-guide/object-storage/section_swift-storage-node.xml23(para)
msgid ""
@@ -7928,7 +7928,7 @@ msgstr ""
#: ./doc/install-guide/object-storage/section_swift-storage-node.xml98(para)
msgid ""
"Edit the <filename>/etc/fstab</filename> file and add the following to it:"
msgstr ""
msgstr "<filename>/etc/fstab</filename> 파일을 수정하고 다음 것들을 추가합니다:"
#: ./doc/install-guide/object-storage/section_swift-storage-node.xml104(para)
msgid "Mount the devices:"
@@ -7938,7 +7938,7 @@ msgstr ""
msgid ""
"Edit the <filename>/etc/rsyncd.conf</filename> file and add the following to"
" it:"
msgstr ""
msgstr "<filename>/etc/rsyncd.conf</filename> 파일을 수정하고 다음 것들을 추가합니다:"
#: ./doc/install-guide/object-storage/section_swift-storage-node.xml136(para)
#: ./doc/install-guide/object-storage/section_swift-storage-node.xml216(para)
@@ -8237,7 +8237,7 @@ msgstr "<literal>swift-init</literal> 명령에 대해 더 알아보려면 다
msgid ""
"This section describes how to verify operation of the Object Storage "
"service."
msgstr ""
msgstr "이 섹션에서는 오브젝트 스토리지 서비스의 동작을 확인하는 방법을 설명합니다."
#: ./doc/install-guide/object-storage/section_swift-verify.xml19(para)
msgid "Show the service status:"
@@ -8288,7 +8288,7 @@ msgid ""
"<link "
"href=\"http://docs.openstack.org/developer/swift/deployment_guide.html\">Deployment"
" Guide</link>."
msgstr ""
msgstr "이 섹션에서는 스토리지 노드 상에서 작동하는 계정, 컨테이너, 오브젝트 서비스의 요청을 다루는 프록시 서비스를 설치하고 설정하는 방법을 설명합니다. 간단히 하기위해, 이 설정은 컨트롤러 노드에 프록시 서버를 설치하고 설정합니다. 하지만, 스토리지 노드로 네트워크 연결이 가능한 어떤 노드라도 프록시 서비스를 구동할 수 있습니다. 게다가, 성능 증가와 여분을 위해 여러 노드에 프록시 서비스를 설치하고 설정할 수 있습니다. 더 많은 정보는, <link href=\"http://docs.openstack.org/developer/swift/deployment_guide.html\">Deployment Guide</link>를 보십시오."
#: ./doc/install-guide/object-storage/section_swift-controller-node.xml20(para)
msgid ""

30
doc/user-guide-admin/locale/ja.po
View File

@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-01-14 19:59+0000\n"
"PO-Revision-Date: 2015-01-14 16:19+0000\n"
"POT-Creation-Date: 2015-01-22 05:45+0000\n"
"PO-Revision-Date: 2015-01-21 14:45+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
@@ -373,7 +373,7 @@ msgstr "groupName"
#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml69(para)
#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml104(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml72(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml119(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml122(para)
#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml17(para)
#: ./doc/user-guide-admin/section_cli_keystone_services.xml102(para)
msgid "For example:"
@@ -2380,8 +2380,8 @@ msgstr "現在のテナントの全ユーザーを表示するには、以下を
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml40(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml84(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml103(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml118(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml132(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml121(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml135(replaceable)
msgid "tenantID"
msgstr "tenantID"
@@ -2696,34 +2696,38 @@ msgid "Administrative users can edit and update Block Storage service quotas."
msgstr "管理ユーザーは、Block Storage のクォータを編集、更新できます。"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml102(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml131(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml134(para)
msgid "Clear per-tenant quota limits:"
msgstr "テナントごとのクォータ制限を解除します。"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml106(para)
msgid ""
"To update a default value for a new project, update the property in the "
"<filename>/etc/cinder/cinder.conf</filename> file."
msgstr "新しいプロジェクトのデフォルト値を更新するために、<filename>/etc/cinder/cinder.conf</filename> ファイルのプロパティを更新します。"
"<literal>cinder.quota</literal> section of the "
"<filename>/etc/cinder/cinder.conf</filename> file. For more information, see"
" the <link href=\"http://docs.openstack.org/trunk/config-reference/content"
"/ch_configuring-openstack-block-storage.html\">Block Storage Configuration "
"Reference</link>."
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml112(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml115(para)
msgid ""
"To update Block Storage service quotas, place the tenant ID in a variable:"
msgstr "Block Storage のクォータを更新して、テナント ID を変数に設定します。"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml114(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml117(replaceable)
msgid "tenantName"
msgstr "tenantName"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml117(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml120(para)
msgid "Update a particular quota value:"
msgstr "特定のクォータ値を更新します。"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml118(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml121(replaceable)
msgid "quotaName"
msgstr "quotaName"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml118(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml121(replaceable)
msgid "NewValue"
msgstr "NewValue"

20
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: 2015-01-15 06:13+0000\n"
"POT-Creation-Date: 2015-01-22 06:14+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"
@@ -261,7 +261,7 @@ msgstr ""
msgid "groupName"
msgstr ""
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:76(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:112(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:175(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:196(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:69(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:104(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:72(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:119(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:17(para) ./doc/user-guide-admin/section_cli_keystone_services.xml:102(para)
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:76(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:112(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:175(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:196(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:69(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:104(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:72(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:122(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:17(para) ./doc/user-guide-admin/section_cli_keystone_services.xml:102(para)
msgid "For example:"
msgstr ""
@@ -1747,7 +1747,7 @@ msgstr ""
msgid "To display all current users for a tenant, run:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:40(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:84(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:103(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:118(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:132(replaceable)
#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:40(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:84(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:103(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:121(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:135(replaceable)
msgid "tenantID"
msgstr ""
@@ -1987,31 +1987,31 @@ msgstr ""
msgid "Administrative users can edit and update Block Storage service quotas."
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:102(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:131(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:102(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:134(para)
msgid "Clear per-tenant quota limits:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:106(para)
msgid "To update a default value for a new project, update the property in the <filename>/etc/cinder/cinder.conf</filename> file."
msgid "To update a default value for a new project, update the property in the <literal>cinder.quota</literal> section of the <filename>/etc/cinder/cinder.conf</filename> file. For more information, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-block-storage.html\">Block Storage Configuration Reference</link>."
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:112(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:115(para)
msgid "To update Block Storage service quotas, place the tenant ID in a variable:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:114(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:117(replaceable)
msgid "tenantName"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:117(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:120(para)
msgid "Update a particular quota value:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:118(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:121(replaceable)
msgid "quotaName"
msgstr ""
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:118(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:121(replaceable)
msgid "NewValue"
msgstr ""

90
doc/user-guide/locale/fr.po
View File

@@ -11,8 +11,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-01-08 20:45+0000\n"
"PO-Revision-Date: 2015-01-08 20:39+0000\n"
"POT-Creation-Date: 2015-01-22 05:45+0000\n"
"PO-Revision-Date: 2015-01-22 00:52+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
"MIME-Version: 1.0\n"
@@ -512,6 +512,92 @@ msgid ""
"Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml4(title)
msgid "Pseudo-hierarchical folders and directories"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml5(para)
msgid ""
"Although you cannot nest directories in OpenStack Object Storage, you can "
"simulate a hierarchical structure within a single container by adding "
"forward slash characters (<literal>/</literal>) in the object name. To "
"navigate the pseudo-directory structure, you can use the "
"<code>delimiter</code> query parameter. This example shows you how to use "
"pseudo-hierarchical folders and directories."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml14(para)
msgid ""
"In this example, the objects reside in a container called "
"<code>backups</code>. Within that container, the objects are organized in a "
"pseudo-directory called <code>photos</code>. The container name is not "
"displayed in the example, but it is a part of the object URLs. For instance,"
" the URL of the picture <code>me.jpg</code> is "
"<uri>https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me.jpg</uri>."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml24(title)
msgid "List pseudo-hierarchical folders request: HTTP"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml25(para)
msgid ""
"To display a list of all the objects in the storage container, use without a"
" delimiter or prefix."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml29(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"requested list of the objects."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml39(para)
msgid ""
"Use the delimiter parameter to limit the displayed results. To use "
"<code>delimiter</code> with pseudo-directories, you must use the parameter "
"slash (<literal>/</literal>)."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml43(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"requested matching objects. Because you use the slash, only the pseudo-"
"directory <code>photos/</code> displays. The returned values from a slash "
"<code>delimiter</code> query are not real objects. They have a content-type "
"of <literal>application/directory</literal> and are in the "
"<literal>subdir</literal> section of JSON and XML results."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml53(para)
msgid ""
"Use the <code>prefix</code> and <code>delimiter</code> parameters to view "
"the objects inside a pseudo-directory, including further nested pseudo-"
"directories."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml57(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"objects and pseudo-directories within the top level pseudo-directory."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml63(para)
msgid ""
"You can create an unlimited number of nested pseudo-directories. To navigate"
" through them, use a longer <code>prefix</code> parameter coupled with the "
"<code>delimiter</code> parameter. In this sample output, there is a pseudo-"
"directory called <code>dogs</code> within the pseudo-directory "
"<code>animals</code>. To navigate directly to the files contained within "
"<code>dogs</code>, enter the following command:"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml73(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"objects and pseudo-directories within the nested pseudo-directory."
msgstr ""
#: ./doc/user-guide/section_object-api-create-large-objects.xml7(title)
msgid "Large objects"
msgstr ""

90
doc/user-guide/locale/ja.po
View File

@@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-01-08 20:45+0000\n"
"PO-Revision-Date: 2015-01-08 20:39+0000\n"
"POT-Creation-Date: 2015-01-22 05:45+0000\n"
"PO-Revision-Date: 2015-01-22 00:52+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
@@ -508,6 +508,92 @@ msgid ""
"Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr "ベアメタルノードの詳細を表示するために、<placeholder-1/> コマンドを使用します。"
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml4(title)
msgid "Pseudo-hierarchical folders and directories"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml5(para)
msgid ""
"Although you cannot nest directories in OpenStack Object Storage, you can "
"simulate a hierarchical structure within a single container by adding "
"forward slash characters (<literal>/</literal>) in the object name. To "
"navigate the pseudo-directory structure, you can use the "
"<code>delimiter</code> query parameter. This example shows you how to use "
"pseudo-hierarchical folders and directories."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml14(para)
msgid ""
"In this example, the objects reside in a container called "
"<code>backups</code>. Within that container, the objects are organized in a "
"pseudo-directory called <code>photos</code>. The container name is not "
"displayed in the example, but it is a part of the object URLs. For instance,"
" the URL of the picture <code>me.jpg</code> is "
"<uri>https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me.jpg</uri>."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml24(title)
msgid "List pseudo-hierarchical folders request: HTTP"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml25(para)
msgid ""
"To display a list of all the objects in the storage container, use without a"
" delimiter or prefix."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml29(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"requested list of the objects."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml39(para)
msgid ""
"Use the delimiter parameter to limit the displayed results. To use "
"<code>delimiter</code> with pseudo-directories, you must use the parameter "
"slash (<literal>/</literal>)."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml43(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"requested matching objects. Because you use the slash, only the pseudo-"
"directory <code>photos/</code> displays. The returned values from a slash "
"<code>delimiter</code> query are not real objects. They have a content-type "
"of <literal>application/directory</literal> and are in the "
"<literal>subdir</literal> section of JSON and XML results."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml53(para)
msgid ""
"Use the <code>prefix</code> and <code>delimiter</code> parameters to view "
"the objects inside a pseudo-directory, including further nested pseudo-"
"directories."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml57(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"objects and pseudo-directories within the top level pseudo-directory."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml63(para)
msgid ""
"You can create an unlimited number of nested pseudo-directories. To navigate"
" through them, use a longer <code>prefix</code> parameter coupled with the "
"<code>delimiter</code> parameter. In this sample output, there is a pseudo-"
"directory called <code>dogs</code> within the pseudo-directory "
"<code>animals</code>. To navigate directly to the files contained within "
"<code>dogs</code>, enter the following command:"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml73(para)
msgid ""
"The system returns status code 2xx (between 200 and 299, inclusive) and the "
"objects and pseudo-directories within the nested pseudo-directory."
msgstr ""
#: ./doc/user-guide/section_object-api-create-large-objects.xml7(title)
msgid "Large objects"
msgstr ""

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

@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-01-09 06:12+0000\n"
"POT-Creation-Date: 2015-01-22 06:14+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"
@@ -353,6 +353,54 @@ msgstr ""
msgid "Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:4(title)
msgid "Pseudo-hierarchical folders and directories"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:5(para)
msgid "Although you cannot nest directories in OpenStack Object Storage, you can simulate a hierarchical structure within a single container by adding forward slash characters (<literal>/</literal>) in the object name. To navigate the pseudo-directory structure, you can use the <code>delimiter</code> query parameter. This example shows you how to use pseudo-hierarchical folders and directories."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:14(para)
msgid "In this example, the objects reside in a container called <code>backups</code>. Within that container, the objects are organized in a pseudo-directory called <code>photos</code>. The container name is not displayed in the example, but it is a part of the object URLs. For instance, the URL of the picture <code>me.jpg</code> is <uri>https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me.jpg</uri>."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:24(title)
msgid "List pseudo-hierarchical folders request: HTTP"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:25(para)
msgid "To display a list of all the objects in the storage container, use without a delimiter or prefix."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:29(para)
msgid "The system returns status code 2xx (between 200 and 299, inclusive) and the requested list of the objects."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:39(para)
msgid "Use the delimiter parameter to limit the displayed results. To use <code>delimiter</code> with pseudo-directories, you must use the parameter slash (<literal>/</literal>)."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:43(para)
msgid "The system returns status code 2xx (between 200 and 299, inclusive) and the requested matching objects. Because you use the slash, only the pseudo-directory <code>photos/</code> displays. The returned values from a slash <code>delimiter</code> query are not real objects. They have a content-type of <literal>application/directory</literal> and are in the <literal>subdir</literal> section of JSON and XML results."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:53(para)
msgid "Use the <code>prefix</code> and <code>delimiter</code> parameters to view the objects inside a pseudo-directory, including further nested pseudo-directories."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:57(para)
msgid "The system returns status code 2xx (between 200 and 299, inclusive) and the objects and pseudo-directories within the top level pseudo-directory."
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:63(para)
msgid "You can create an unlimited number of nested pseudo-directories. To navigate through them, use a longer <code>prefix</code> parameter coupled with the <code>delimiter</code> parameter. In this sample output, there is a pseudo-directory called <code>dogs</code> within the pseudo-directory <code>animals</code>. To navigate directly to the files contained within <code>dogs</code>, enter the following command:"
msgstr ""
#: ./doc/user-guide/section_object-api-pseudo-hier-folders.xml:73(para)
msgid "The system returns status code 2xx (between 200 and 299, inclusive) and the objects and pseudo-directories within the nested pseudo-directory."
msgstr ""
#: ./doc/user-guide/section_object-api-create-large-objects.xml:7(title)
msgid "Large objects"
msgstr ""